This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 9848 - legacy color values should not require handling of CSS2 system colors
Summary: legacy color values should not require handling of CSS2 system colors
Status: RESOLVED WORKSFORME
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-04 00:17 UTC by L. David Baron (Mozilla)
Modified: 2010-10-04 14:46 UTC (History)
4 users (show)

See Also:


Attachments

Description L. David Baron (Mozilla) 2010-06-04 00:17:10 UTC
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.)