Replies: 1 comment
-
|
Thank you for providing this input @smg6511! Last year, I tried to add some keyboard navigation optimisation to the manager. In doing so, I had to rearrange some elements because the z-index was very confusing. Based on this, there were some follow-up bugs. Mainly, the navigation should be completely rewritten with modern standards like CSS variables and anchor points. However, this is mostly a task for version 4. Would it be useful to split the navigation items into layers and give each layer a name? Here is an example of what I mean: https://medium.com/@mevbg/modern-z-index-management-evolving-a-classic-sass-pattern-0042724da65c |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It occurs to me that maybe we should establish a range of z-indexes that core MODX uses, say 0-100 and maybe one high one meant to “override” all page elements, including anything generated by an Extra (maybe 999 for system modals and such). There's no reason to have ridiculously-high z-indexes if there's a rule for how we use them. Then it would be up to Extra devs to adhere to these ranges, using 101-998 for placing their elements above the core layout or below that range to weave something between core elements (unlikely to be done, but possible). Anyway, just an idea for future consideration; what are your thoughts?
Beta Was this translation helpful? Give feedback.
All reactions