Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Some of the styling in overlay-child.css is affecting the label within the Overlay listing on the Extend page. This is because the label has an id of 'overlay'.
I'm not sure if this is a fix for the Overlay module because I'm not sure why we are printing module id's on the labels in the first place. If it's for the performance of Javascript filtering then a data attribute seems more appropriate.
Comment | File | Size | Author |
---|---|---|---|
#7 | overlay-1919564-7.patch | 1.29 KB | rajneeshb |
#3 | Screen Shot 2013-02-17 at 18.31.55.png | 17.65 KB | LewisNyman |
#2 | drupal8.system-modules-id.2.patch | 898 bytes | sun |
Screen Shot 2013-02-17 at 15.49.56.png | 59.83 KB | LewisNyman |
Comments
Comment #1
sunThat #id is not used by the module list search/filter.
I quickly checked the code, but it looks like it gets auto-generated by Form API. But then again, such IDs should normally be "edit-foo", not just "foo".
Something is completely wrong there.
Comment #2
sunGotcha.
Comment #3
LewisNymanPatch applies cleanly, everything is look great.
Comment #4
tstoecklerThese IDs were added intentionally in #1828464: Add same-page links to the Module page, so this needs to at least mention why it is OK to revert that instead of changing the IDs to fix the bug.EDIT: That was BS, sorry...
Comment #5
tstoecklerReverting status
Comment #6
webchickThat's a pretty hilarious bug. :)
However, it totally undoes #184010: Add #anchors to modules administration page which was done for a reason, so I think the better fix is to preface with module- which is what earlier versions of that patch did.
That should be pretty easy to do, so tagging Novice.
Comment #7
rajneeshb CreditAttribution: rajneeshb commentedI have checked and found that there are two ID named as "overlay" . so I created a patch for overlay module to remove duplicate overlay ID.
Comment #8
tstoecklerI guess we could actually do both, (i.e. change overlay module to use #overlay-wrapper and the modules page to use #module-$module), but this doesn't hurt either.
Comment #9
bleen CreditAttribution: bleen commentedPersonally I like the solution in #7 better than prefacing the module class with "module-" and I dont see any reason why we need to do both.
Comment #10
sunI disagree with the proposed solution.
The bug is that System module violates the CSS namespaces of other modules.
To wit: User module uses #module-[name] CSS IDs on the Permissions page.
This needs to be fixed in the original issue. Marking as duplicate of #184010: Add #anchors to modules administration page