-
Notifications
You must be signed in to change notification settings - Fork 48
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Style changes on table: Rules of ARIA attributes usage by HTML language feature #141
Comments
My bad. The change was... um... half intentional. We should probably remove any custom style from the spec and let basic.css handle the table styling. |
@pgrucza you want to take this one too? At least, have a play with removing the custom style in the spec and seeing if |
I'll have a look ( likely tomorrow ). Is there anything I need to be aware of in your previous changes for the layout ? |
No, nothing that I can think of. |
#133 added |
Sorry, I think I might have confused you... ".simple" is part of basic.css. However, the document is adding "makeup.css", which includes some style rules for table. Those are the ones that need that need to be removed, I think... namely: tr:nth-child(2n+1) {
background-color: #ebebeb;
} Which is conflicting with "simple". |
ok returned tr:nth-child(2n+1) {
background-color: #ebebeb;
} from makeup.css This leaves the blue header row and light blue striping coming from simple. Inline ReSpec 3 CSS For request, "fixing links in ahref and anohref" #143 |
With recent updates to the Editor's Draft there seems to be some styling changes to the table for Rules of ARIA attributes usage by HTML language feature.
The currently published Working Draft has grey table headings and is striped white and grey. Columns are also separated.
The Editor's Draft uses dark blue headings and is striped blue and grey. Columns are not visually separated. A class="simple" has been applied to the table.
I'm wondering if this styling change is intentional or is it a side effect of the recent updates?
The text was updated successfully, but these errors were encountered: