Closed (fixed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
system.module
Priority:
Normal
Category:
Task
Assigned:
Issue tags:
Reporter:
Created:
16 Oct 2012 at 01:25 UTC
Updated:
15 Jan 2015 at 00:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
sunComment #2
sunFeedback, anyone? :)
Comment #3
jessebeach commentedI'm totally behind this. If you don't patch it first, I'll have it in my list to get to.
Comment #4
sunMmm, there's a patch in #0 already? :)
The screenshot shows after btw
Comment #5
Bojhan commentedComment #6
Bojhan commentedOops, yes :)
Comment #7
jessebeach commentedDoh! I was looking for a patch and for some reason just didn't see it.
@sun, one comment, will a
trtag ever not be a direct descendant of atheadtag. Or said another way, why is the direct child selector necessary?Comment #8
sunWell, as you know, history has taught me there's barely a markup situation that doesn't exist in Drupal due to its modular nature.
A nested table in a table header? Who knows?
However, I'm certainly willing to admit and accept that this would be an extreme edge-case that should probably be discouraged in the first place and for which sites need to override system.theme.css if they really want it. :)
So attached patch removes the child selector. :)
Comment #9
sunAre we ready? :)
Comment #10
jessebeach commentedTested and working.
Before:
After:
Comment #11
dries commentedBoth are ugly, but the after is a tiny bit better. ;-)
Comment #12
sunHeh, please bear in mind that the screenshots are showing Stark; i.e., the "anti-theme."
The goal and purpose is to see almost native browser styling in Stark. So what's ugly in reality are the browser default styles, which did not really change since the inception of the WWW (and I think that's on purpose for the most parts).
Technically, even the horizontal row borders are borderline too much styling for Stark, but removing them altogether resulted in a very weird experience, since there wasn't any visual indication of a table anymore.
In any case, the new styles are much easier to adjust and override in a theme and finally remove the weird default background color, which is the most offending part.
Comment #13
webchickThe after makes sense to me. Themers are constantly saying they don't want to override core's assumptions, so fewer assumptions == more betterer. :)
Can't really review the code parts, but I assume jessebeach did in her review. Therefore...
Committed and pushed to 8.x. Thanks!
Comment #14
sunNext one in line: #1825446: Simplify and remove stone-age CSS styling for tabs :)
Comment #15
tim.plunkettThis did some odd things to the Block UI in Seven.
Before:

After:

Comment #16
sunI have to admit that wasn't intended, but I actually don't see what's broken or not to like there.
The only difference between before and after is that a border-bottom is applied to the region header table rows.
And in fact, when there are multiple blocks within a region, that provides some helpful visual guidance for as to where a region's group starts and where it ends:
Thus, moving back to fixed.
Comment #18
yesct commentedfixing tags so can delete the lesser used ones.