Repository navigation
Remove color-rendering CSS property #647
Description
https://www.w3.org/TR/SVG2/painting.html#ColorRendering
It has no normative requirements.
Only Chrome implements passes all the WPT tests for it of it and I don't know what they do with it beyond parsing it.
Activity
dholbert commentedon Feb 28, 2019
@progers : hi! biesi told me you might be a person who could weigh in here on the Chrome side -- could you tell us if Chrome actually does anything with this property? (And would you be OK removing it?)
dholbert commentedon Feb 28, 2019
(biesi says @fsoder might also be able to weigh in on this)
fsoder commentedon Feb 28, 2019
Blink does not actually do anything with the
color-renderingproperty. It would hopefully be OK to remove it.AmeliaBR commentedon Mar 1, 2019
@dirkschulze @Tavmjong is this property used in graphical SVG editors to your knowledge?
The
color-renderingproperty is about hinting to the user agent about performance trade-offs, though, so I can't see it being that relevant in print media. So if it has no impact in browsers, that would be a good argument for removing it.CSS Color Level 4 currently includes a
color-adjustproperty that has a lot of similarities tocolor-rendering, but is defined in terms of modern device behavior. I'm not sure if there is any value in keepingcolor-renderingaround as a legacy synonym. It would depend on whether it's actually being used in content.dirkschulze commentedon Mar 4, 2019
As far as I can tell, Adobe products neither import nor generate
color-rendering.css-meeting-bot commentedon Mar 4, 2019
The SVG Working Group just discussed
remove color-rendering, and agreed to the following:RESOLUTION: Drop color-rendering and update parsing tests. Revisit on objections.The full IRC log of that discussion
<krit> topic: remove color-rendering<krit> GitHub: https://github.com//issues/647
<krit> AmeliaBR: one of the SVG 1.1 hint properties. Authors could tell engine to optimise speed or quality.
<krit> AmeliaBR: AFAIK no UA does actively support it.
<krit> AmeliaBR: Blink parses it at least
<krit> AmeliaBR: Firefox doesn't so.
<krit> myles: what was the original intention?
<krit> myles: what could an implementation do?
<krit> AmeliaBR: color interpolation, compositing
<krit> AmeliaBR: linearRGB might be faster than sRGB... but that might no longer be true.
<krit> myles: I would be comfortable with removing this.
<krit> krit: Don;t know Adobe product that makes use of it on either import or generating SVG documents.
<krit> AmeliaBR: There is no legacy issue. It is not breaking anything.
<krit> krit: we could get a resolution and see if we get objections.
<krit> AmeliaBR: Safari just accepts the camel case version.
<krit> AmeliaBR: ... for keywards
<krit> myles: checking if webkit does anything with it...
<krit> AmeliaBR: minimal action would be to mark it as at-risk
<krit> myles: don't see any use in WebKit
<krit> myles: 's implementation itself beside computed style
<krit> RESOLUTION: Drop color-rendering and update parsing tests. Revisit on objections.
<krit> krit: while we are at it, what about color-interpolation.
<krit> AmeliaBR: need to check comments
<krit> AmeliaBR: IIRC only Batik supported Color-interpolation.
svgeesus commentedon May 7, 2019
OK, I will make a PR removing this.
Remove color-rendering CSS property as resolved by the WG. Fixes #647