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 29317 - "Should author specified values be normalized fo..."
Summary: "Should author specified values be normalized fo..."
Status: NEW
Alias: None
Product: CSS
Classification: Unclassified
Component: CSSOM (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Simon Pieters
QA Contact: public-css-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-12-01 09:45 UTC by Ms2ger
Modified: 2017-03-13 13:18 UTC (History)
0 users

See Also:

Attachments

Description Ms2ger 2015-12-01 09:45:59 UTC 
https://drafts.csswg.org/cssom-1/#serializing-css-values

[[
Should author specified values be normalized for case? Or should original case be preserved? 
]]

Filing for bookkeeping.
Comment 1 Ms2ger 2015-12-01 10:10:33 UTC 
cssstyledeclaration-csstext.html allows both results as of <https://github.com/w3c/csswg-test/pull/964>; should be updated once the spec is decided.
Comment 2 Simon Pieters 2017-03-13 13:18:13 UTC 
Quick test:

http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4830

* WebKit, Blink, Edge 13:
  log: rgb(255, 0, 0)
  log: red
* Gecko:
  log: rgb(255, 0, 0)
  log: ReD

So two things:

* rgb() syntax is normalized everywhere; the exact author-specified input is not preserved.

* Color keywords are lowercased everywhere except Gecko. I suggest Gecko should change.