13019 2011-06-22 21:17:28 +0000 Organization of the user agent style sheet section makes it near-impossible to see whether it's correct 2011-08-04 05:16:06 +0000 1 1 1 Unclassified HTML WG LC1 HTML5 spec unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#the-css-user-agent-style-sheet-and-presentational-hints P3 critical --- 1 contributor ian ayg bzbarsky ian mike Ms2ger public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 50118 0 contributor 2011-06-22 21:17:28 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/rendering.html Multipage: http://www.whatwg.org/C#the-css-user-agent-style-sheet-and-presentational-hints Complete: http://www.whatwg.org/c#the-css-user-agent-style-sheet-and-presentational-hints Comment: Organization of the user agent style sheet section makes it near-impossible to see whether it's correct Posted from: 71.184.125.56 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:7.0a1) Gecko/20110621 Firefox/7.0a1 50131 1 bzbarsky 2011-06-22 22:09:10 +0000 In particular, the section is organized not by element(s) being styled but by properties being set. Just determining what the border styles for tables look like involves reading two separate sections: "Fonts and Colors", "Punctuation and Decorations". In the latter, two completely separate chunks of style information separated by prose need to be read. It would make more sense to me, and make the specification much more reviewable, to have a section on table styles, a section on list styles, a section on alignment, a section on display types, and then see what's left. 50173 2 ayg 2011-06-23 16:51:26 +0000 How would you organize it by the element? Often one rule affects a zillion elements. Should it be split into lots of rules? 50175 3 bzbarsky 2011-06-23 17:02:01 +0000 I proposed a specific start to the organization in comment 1. For the rest, it depends. There's clearly no need to have more than one rule for [disabled]. 50176 4 bzbarsky 2011-06-23 17:03:05 +0000 Maybe what's really needed here is organization by what rules are meant to do (as opposed to what properties they set to accomplish that goal, which is not quite the same thing). The various table border rules are all meant to work together coherently, and should be organized that way. 50578 5 ian 2011-07-02 00:12:53 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments. I would appreciate careful review of the diff below to make sure I didn't screw anything up. Also, this is just a first attempt at reorganising this to make it more usable. If you can think of anything to make it even more usable, please don't hesitate to file more bugs on this. 50579 6 contributor 2011-07-02 00:13:16 +0000 Checked in as WHATWG revision r6276. Check-in comment: Attempt to reorganise the rendering section to make it more usable for implementors http://html5.org/tools/web-apps-tracker?from=6275&to=6276 53659 7 mike 2011-08-04 05:16:06 +0000 mass-move component to LC1