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
Overhaul of the user panel menu #4603
Conversation
Favico.js was used exclusively for the notification badge in the favicon, but was replaced with a lightweight implementation. The user panel items cannot be properly mapped to the new implementations, if a custom version of `pageHeaderUser.tpl` is being used, then they are screwed anyway.
``` cp node_modules/tabbable/dist/index.umd.min.js wcfsetup/install/files/js/3rdParty/focus-trap/ cp node_modules/tabbable/dist/index.umd.min.js.map wcfsetup/install/files/js/3rdParty/focus-trap/ ``` ``` cp node_modules/focus-trap/dist/focus-trap.umd.min.js wcfsetup/install/files/js/3rdParty/focus-trap/ cp node_modules/focus-trap/dist/focus-trap.umd.min.js.map wcfsetup/install/files/js/3rdParty/focus-trap/ ```
It doesn't play nicely with the UI/UX concept
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eyeballed everything, except for pageHeaderUser.tpl. The changes are just too large in there.
wcfsetup/install/files/lib/data/moderation/queue/ModerationQueueAction.class.php
Outdated
Show resolved
Hide resolved
wcfsetup/install/files/lib/data/user/notification/UserNotificationAction.class.php
Outdated
Show resolved
Hide resolved
The commit c9e8db8 might not be immediately obvious, but this is pretty much what the previous implementation does by slapping |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As far as I'm qualified to tell this LGTM now. I did not perform a test, this was a review purely based on the diff.
The menu has been rebuilt from the ground up with simplicity, consistent styling and a11y in mind. It introduces a set of new style variables to avoid the pitfall of deriving colors from different elements just because the happen to fit in nicely in the default style.
This change is the first step towards the new mobile menu which will be built on top of this. For now the conversation menu has been left unchanged to serve as a blueprint for the backwards compatibility layer.