The admin_menu_toolbar shortcuts toolbar has unaligned links that triggers my OCD.
As you see top padding is bigger than bottom by couple pixels. It's caused by modules/system/system.menus.css
:
li.expanded, li.collapsed, li.leaf {
padding: 0.2em 0.5em 0 0;
}
This problem does not appear on default Drupal installation stock module Toolbar and icons appear to be aligned correctly, because the system.menus.css
rule is overwritten by modules/toolbar/toolbar.css
:
#toolbar, #toolbar * {
padding: 0;
}
Which is why we have this problem in admin_menu because Toolbar is disabled and no more toolbar.css rules.
This is with admin_menu disabled, with system toolbar (aligned as should be, also with bright white text color, which is changed to duller version in admin_menu for some reason):
Also another: All the links on admin menu and shortcuts menu when you hover has round borders background with no underline, but the Edit shortcuts button is underline text with no background, why?
Anyway cheers!
Comment | File | Size | Author |
---|---|---|---|
aligned-shortcuts-links-toolbar.png | 4.34 KB | vibrasphere | |
unaligned-shortcuts-links.png | 5.88 KB | vibrasphere |
Comments
Comment #2
truls1502I am sorry for no reply until now.
There are many issues regarding this module admin_menu which is a bit difficult for us to follow up since some of the issues might be already outdated, or is already fixed by the module or any other modules or itself core which means that the problem might no longer need to be fixed.
We can see that the issue has been created for a few years ago, I hope it is okay for you that I am postponing the issue, and give you around two weeks. If you still face the problem, could you tell us the step by step when until you get the error message or what is frustrated you, and a list of modules you are using related to admin_menu and a screenshot that might help us? So it makes us easier to reproduce your issue.
However, after two weeks with no feedback - we will close this issue. So in case, you noticed it after the issue is closed, do not hesitate to reopen it like and fill information which is mentioned above.
So before giving us a feedback, do you mind to test it again with our latest 7.x-3.x-dev?
Thank you for understanding! :)
Comment #3
vibrasphere CreditAttribution: vibrasphere commentedthis is some sad copy pasta
Comment #4
truls1502Hi @vibrasphere,
Yes, I am sorry with the bothering standard message from me. I have recently jumped into the project, so I start now to clean the module project, so it is not easy to handle with the old issues.
Let me know what happens if you are using the latest version 7.x-3.x-dev, is it fixed now? I believe this one has fixed your problem, and please let us know. :)
Also, feel free to change the status what you might feel right so we can catch up and do our best job with this module. :)
Comment #5
vibrasphere CreditAttribution: vibrasphere commentedComment #7
truls1502