- From: <bugzilla@jessica.w3.org>
- Date: Fri, 04 Jun 2010 00:17:10 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9848 Summary: legacy color values should not require handling of CSS2 system colors Product: HTML WG Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: dbaron@dbaron.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html@w3.org As I wrote in http://lists.whatwg.org/pipermail/whatwg-whatwg.org/2010-May/026449.html : The "rules for parsing a legacy color value" in http://www.whatwg.org/specs/web-apps/current-work/complete/common-microsyntaxes.html#rules-for-parsing-a-legacy-color-value specify that CSS2 system colors should be accepted, and that they should be converted to a simple color. It seems like a substantial amount of work to get dynamic change handling correct for this case, since system colors can change dynamically when the user changes system appearance. I'd really like to avoid having to add dynamic change handling for this, and I'd also like to avoid having to make system colors dynamic in CSS but static in HTML. (The current wording in the spec seems to mandate that they are static, which seems like a bad idea in itself.) -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Friday, 4 June 2010 00:17:12 UTC