New issue
Advanced search Search tips

Issue 901669 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 3
Type: Bug



Sign in to add a comment

CSS: image-rendering not accepting optimizeSpeed optimizeQuality

Project Member Reported by ericwilligers@chromium.org, Nov 4

Issue description

The SVG 1.1 property image-quality accepts
auto | optimizeSpeed | optimizeQuality
https://www.w3.org/TR/SVG11/painting.html#ImageRenderingProperty

Blink has code for optimizespeed and optimizequality, but if
I attempt to use those values, the specified value is unset and
the computed value is auto.
https://jsfiddle.net/ericwilligers/8ayzskhn/

Note that CSS Images defines a different set of values
https://drafts.csswg.org/css-images/#the-image-rendering
auto | smooth | high-quality | crisp-edges | pixelated
but no browser supports smooth or high-quality


 
Status: Available (was: Untriaged)
Owner: f...@opera.com
Status: Assigned (was: Available)
Looks like the parser doesn't recognize them but we list them in the property description (css_properties.json5.) I can add them. (Or remove them I suppose... spec says they should be recognized, and Gecko does so...)
I suggest we behave consistently with Firefox and Safari.

I've requested clarity on smooth | high-quality
https://github.com/w3c/csswg-drafts/issues/3283

Summary: CSS: image-rendering not accepting optimizeSpeed optimizeQuality (was: CSS: image-quality not accepting optimizeSpeed optimizeQuality)

Sign in to add a comment