Support the 'optimizeSpeed' value to 'image-rendering' as an alias for/equivalent of 'pixelated'
Reported by
edema...@gmail.com,
Oct 27 2016
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36 Example URL: http://tavmjong.free.fr/SVG/IMAGE_RENDERING/index.html Steps to reproduce the problem: 1. Load any SVG file with an embedded image that has a style of style="image-rendering:optimizeSpeed" What is the expected behavior? The image should be pixelated like pixel art (using nearest-neighbor rendering). What went wrong? The image is scaled smoothly, as if the image-rendering style wasn't present. Does it occur on multiple sites: N/A Is it a problem with a plugin? N/A Did this work before? No Does this work in other browsers? N/A Chrome version: 53.0.2785.143 Channel: n/a OS Version: 10.0 Flash Version: Shockwave Flash 23.0 r0 SVG defines styles like style="image-rendering:optimizeSpeed" [https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/image-rendering]. But this style is unsupported by Chrome. These options differs from CSS's image-rendering style [https://developer.mozilla.org/en-US/docs/Web/CSS/image-rendering], such as image-rendering:pixelated, which *is* supported by Chrome. Ideally Chrome should support all the options (SVG and CSS); see the table of support at https://developer.mozilla.org/en-US/docs/Web/CSS/image-rendering But in particular it is a bug to not support the SVG style in an SVG object.
,
Oct 28 2016
A better reference might have been CSS Image Values (...): "This property previously accepted the values optimizeSpeed and optimizeQuality. These are now deprecated; a user agent must accept them as valid values but must treat them as having the same behavior as pixelated and auto respectively, and authors must not use them." [https://drafts.csswg.org/css-images-3/#the-image-rendering] So I guess we should consider adding "support" for 'optimizeSpeed' per the spec quote above. Too bad Gecko's 'pixelated' implementation seems to have been bogged down by technicalities...
,
Oct 28 2016
Sure, here is a jsfiddle: https://jsfiddle.net/xezh44mf/2/ Both optimizeSpeed and pixelated should look like a checkerboard, with no fuzzyness. Amusingly, Firefox is pretty much the reverse: old-fashioned optimizeSpeed works, but pixelated does not.
,
Nov 1 2016
,
May 29 2018
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 29 2018
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by hdodda@chromium.org
, Oct 28 2016Labels: Needs-Feedback