Closed
Bug 589615
Opened 16 years ago
Closed 15 years ago
Put all preshints (at least for HTML, independent of document type) in the author level
Categories
(Core :: CSS Parsing and Computation, defect, P2)
Tracking
()
RESOLVED
FIXED
mozilla2.0b10
People
(Reporter: darxus-mozillabug, Assigned: bzbarsky)
References
(Blocks 1 open bug, )
Details
(Keywords: html5)
Attachments
(3 files)
|
15.84 KB,
patch
|
dbaron
:
review+
|
Details | Diff | Splinter Review |
|
8.98 KB,
patch
|
dbaron
:
review+
|
Details | Diff | Splinter Review |
|
18.08 KB,
patch
|
dbaron
:
approval2.0+
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b4pre) Gecko/20100817 Minefield/4.0b4pre
Build Identifier:
Fails test.
Reproducible: Always
Blocks: ietestcenter
Version: unspecified → Trunk
| Assignee | ||
Comment 1•16 years ago
|
||
This test is either assuming that CSS2.1 section 6.4.4 includes XHTML when it says "HTML" (I see no basis for this assumption) or that default link styling is in the UA level in the cascade. In Gecko it's in the user level.
So, unless the assumption about CSS2.1 is correct for some reason I missed, the test is broken and we need to get the IE folks to fix it.
Component: General → Style System (CSS)
QA Contact: general → style-system
| Assignee | ||
Comment 2•16 years ago
|
||
Ok, the HTML5 spec does have verbiage about this. http://www.whatwg.org/specs/web-apps/current-work/complete/rendering.html#the-css-user-agent-style-sheet-and-presentational-hints second paragraph of the introduction, in particular.
Furthermore, SVG says that its preshints should go in the author level too (SVG 1.1, section 6.4, paragraph starting "For user agents that support CSS, the presentation attributes must be translated". We don't do that currently.
David, how would you feel about just putting all preshints in the author level?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: (ietestcenter) HTML5 XHTML5 2/9: Test for link="yellow" on body → Put all preshints (at least for HTML, independent of document type) in the author level
| Assignee | ||
Updated•15 years ago
|
Assignee: nobody → bzbarsky
Priority: -- → P2
Yes, I think we should change this.
The CSS spec was never really explicit here; the XHTML WG clearly wanted the XML-like option, but we should make it HTML-like.
| Assignee | ||
Comment 5•15 years ago
|
||
| Assignee | ||
Comment 6•15 years ago
|
||
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [need review]
| Assignee | ||
Updated•15 years ago
|
Attachment #484226 -
Flags: review?(dbaron)
| Assignee | ||
Updated•15 years ago
|
Attachment #484227 -
Flags: review?(dbaron)
Blocks: css2.1-tests
| Assignee | ||
Comment 7•15 years ago
|
||
dbaron, do you think we should try to get this in for 2.0?
Comment on attachment 484226 [details] [diff] [review]
part 1. Get rid of the non-HTML preshint level.
Seems like this comment should stay:
>- //Enable/Disable entire author style level (Doc & PresHint levels)
r=dbaron
Attachment #484226 -
Flags: review?(dbaron) → review+
Comment on attachment 484227 [details] [diff] [review]
part 2. Rename the HTML preshint level to just the preshint level, since it's the only preshint level now.
r=dbaron
Attachment #484227 -
Flags: review?(dbaron) → review+
| Assignee | ||
Comment 10•15 years ago
|
||
> Seems like this comment should stay:
Agreed and reinstated.
| Assignee | ||
Comment 11•15 years ago
|
||
This is fairly safe and fixes some reasonably prominent test failures.
Attachment #493894 -
Flags: approval2.0?
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [need review] → [need approval]
Attachment #493894 -
Flags: approval2.0? → approval2.0+
| Assignee | ||
Updated•15 years ago
|
Whiteboard: [need approval] → [need landing]
| Assignee | ||
Comment 12•15 years ago
|
||
Pushed:
http://hg.mozilla.org/mozilla-central/rev/1133df9783f4
http://hg.mozilla.org/mozilla-central/rev/65dfc25b1cae
Status: NEW → RESOLVED
Closed: 15 years ago
Flags: in-testsuite+
Resolution: --- → FIXED
Whiteboard: [need landing]
Target Milestone: --- → mozilla2.0b10
You need to log in
before you can comment on or make changes to this bug.
Description
•