Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
Seven theme
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
21 Feb 2015 at 16:15 UTC
Updated:
12 Mar 2015 at 06:04 UTC
Jump to comment: Most recent, Most recent file


Comments
Comment #1
idebr commentedAttached patch fixes the visual regression. Screencap after:
Comment #2
lewisnymanThanks for the patch. I thought we had a no-js class but we don't...
Instead of undoing the CSS for JS, maybe we can only set the CSS on :not(.js)?
Comment #3
idebr commented@LewisNyman Attached patch uses your suggestion, but I'm hesitant to use this pattern:
- It introduces styling specific for non-javascript users instead of using javascript for progressive enhancement
- It would be the first occurrence of this type of selector in HEAD
Personally I would prefer the approach in #1, but I'll leave the call up to you.
Screenshot with javascript disabled:
Comment #4
lewisnymanThe .no-js class is commonly used on the web, right? The :not(selector) is just a modern equivalent of this. I'd rather not override CSS and the SMACSS principles we've embraced in our coding standards are designed to avoid this kind of CSS. Setting to RTBC and we can at least get a committer's opinion on it.
Comment #5
webchickFrom the look of it, dropbutton.component.css has approximately 50 gazillion
.js .something-somethingrules and zero ":not" rules. Therefore, I think #1 is probably best, though it might be worth a separate issue to discuss whether / how to introduce ":not" syntax.Committed and pushed #1 to 8.0.x. Thanks!