Problem/Motivation
The dropbutton dont follow the css coding standard. Makes it hard for themers to figure out which classes are used by javascript and which are not
[#1887918#separate-concerns]
This issue came up as we were cleaning up templates, in core as part of the banana#2
Proposed resolution
* prefix everything that the dropbutton component required of classnames with .js-
refactore the css, to reflect that and ensure that the css files gets * splitted up in MAT filestructure [#1887922]
* component must be completely functional with the module.css file (or component) and running in stark, with not theme.css files loaded
* component keeps same design when *.theme.css is activated in classy, stark & seven.
dropbutton is placed on these pages
/node/1/edit
/admin/structure/views/view/aggregator_rss_feed/edit/page_1
/admin/structure/types/manage/page/fields
Remaining tasks
User interface changes
API changes
Comment | File | Size | Author |
---|---|---|---|
#3 | dropbottom-2.diff | 43.15 KB | mortendk |
dropbottom.diff | 39.97 KB | mortendk | |
Comments
Comment #2
mortendk CreditAttribution: mortendk commentedComment #3
mortendk CreditAttribution: mortendk commentedstructure in a more BEM like way
Comment #5
LewisNymanClosing as a duplicate of #2278473: Simplify Dropbutton markup in line with our CSS standards, please post the patch there.
Also see: #1899236: Add new Splitbutton render element to eventually replace Dropbutton
Comment #6
mortendk CreditAttribution: mortendk commentedlewis im not sure im agreeing that this is a duplicate of the issue. This is not rewriting the markup this is purely seperating the css names from the js