Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[demo] "dense" prop on submenu headers makes root menu items not consistent #3437

Closed
esistgut opened this issue Jul 21, 2019 · 3 comments
Closed

Comments

@esistgut
Copy link
Contributor

The dense prop used here

<MenuItem dense button onClick={handleToggle}>

produces a "compact" version of the root menu items:

Screenshot from 2019-07-21 18-48-06

while the root menu items without submenus keep the "non compact" aspect:

Screenshot from 2019-07-21 18-49-57

This is the same root menu without the dense prop:

Screenshot from 2019-07-21 18-48-59

I'm not sure if the desired design is "dense everywhere" (parent and child menus) or if the the dense prop should be used only on child menus.

Please note: as you can see this is based on a local prototype using an extracted version of the demo submenu code so there is a chance the demo doesn't show the same behavior. I tried to do the same tests directly on the demo but encountered some difficulties #3436.

@esistgut
Copy link
Contributor Author

esistgut commented Jul 21, 2019

After the restoring of the demo (#3440) I did some additional tests: the problem doesn't show up on the demo because it forces an older version of material-ui (4.0.0-beta.2) on its dependencies. On this version the dense props don't seem to sort any effect. Upgrading to the current version (4.2.1) makes the problem visible.
Screenshot from 2019-07-21 21-36-14

@esistgut esistgut changed the title [v3-alpha, demo?] "dense" prop on submenu headers makes root menu items not consistent [demo] "dense" prop on submenu headers makes root menu items not consistent Jul 21, 2019
@djhi
Copy link
Collaborator

djhi commented Oct 1, 2019

Can't reproduce it on the latest alpha. Can you please confirm it is fixed or provide a codesandbox showing the issue?

@fzaninotto
Copy link
Member

Already fixed in next (#3718)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants