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

Difficult to change listview layout in content section #6430

Closed
bjarnef opened this issue Sep 25, 2019 · 3 comments · Fixed by #6433
Closed

Difficult to change listview layout in content section #6430

bjarnef opened this issue Sep 25, 2019 · 3 comments · Fixed by #6433

Comments

@bjarnef
Copy link
Contributor

bjarnef commented Sep 25, 2019

In content section it is difficult to change listview layout, because it open the "Content" navigation dropdown even you don't hover this button.

Reproduction

Bug summary

In starterkit on Blog node try change listview layout from grid to list layout. It open the dropdown for "Content" navigation before you are able to click the listview layout selector.

Specifics

Umbraco v8.2.0 (latest codebase in v8/dev branch.
Chrome Version 77.0.3865.90

Steps to reproduce

In starterkit on Blog node try change listview layout from grid to list layout. It open the dropdown for "Content" navigation before you are able to click the listview layout selector.

Expected result

It should be possible to click the listview layout selector to change listview layout - just like in media and member section.
The dropdown for "Content" navigation item, should only open when hover the actual navigation item.

Actual result

The dropdown menu for "Content" navigation open before you are able to click the listview layout selector.

2019-09-25_21-48-15

@bjarnef
Copy link
Contributor Author

bjarnef commented Sep 25, 2019

It seems the dropdown is shown when hover this highligted area.

image

@nathanwoulfe
Copy link
Contributor

Problem is due to the hidden list being hidden via opacity, so the element is still present in the DOM and taking up space in the flow - even though the :hover state is applied by hovering the Content button, the list, as a descendant node, can still be hovered.

@nul800sebastiaan
Copy link
Member

Fixed in #6433

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

Successfully merging a pull request may close this issue.

4 participants