Base64 blurry images is too sharp
Reported by
zou...@zouhir.org,
Oct 3 2017
|
|||
Issue description
Chrome Version : 61.0.3163.100
OS Version: OS X 10.12.6
URLs (if applicable) :
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5:
Firefox 4.x:
IE 7/8/9:
What steps will reproduce the problem?
1. Get a 16px width Base64 JPEG or PNG
2. Set it as a `src` for an image tag of let's say 600px width.
What is the expected result?
I expect to see a blurry image with smooth colors behind the blur that are close to the original high-res image.
What happens instead of that?
I do see the blurry image but, in previous Chrome versions, it was OK and smooth as seen in the attachment and to the left. Recent Chrome version is making color spots very crisp and very pixelated.
Please see the issue in these examples:
https://lqip-loader.firebaseapp.com/
https://codepen.io/jmperez/full/Xmzobe
More thoughts:
I thought of a CSS workaround of using `filter: blur(..px)` but I do prefer if the Base64 images where behaving as they've used to behave natively.
Thank you!
UserAgentString: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
,
Oct 4 2017
Able to reproduce the issue on Windows 10, mac 10.12.6 and Ubuntu 14.04 using chrome reported version #61.0.3163.100 and latest canary #63.0.3231.0. Bisect Information: ===================== Good build: 61.0.3163.37 Bad Build : 61.0.3163.38 Note: The good and bad builds are branch builds. Hence, providing the change log from omahaproxy Change Log URL: https://chromium.googlesource.com/chromium/src/+log/61.0.3163.37..61.0.3163.38?pretty=fuller&n=10000 From the above change log suspecting below change Change-Id: Idc42c1a176ebd6394ae23324a37724b82278d9cc Reviewed-on: https://chromium-review.googlesource.com/585404 vmpstr@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: Adding label ReleaseBlock-Stable as it seems to be a recent regression. Thanks...!!
,
Oct 4 2017
Hey, Unfortunately this is going to be the new behavior for Chrome. This is matching other browsers, and improves both memory (in sw) and performance (in both sw and gpu) in Chrome. It sounds like you already have a blur workaround for your use-case as well, which is good. Note that you can read more about our decision here: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/6L_3ZZeuA0M Long term we may consider web platform features for the developers to specify the preferred image filter quality to use, but that's just a discussion right now and we have no concrete plans on implementing this. To reiterate, as it stands this is the new Chrome behavior and thus this bug is a WontFix. |
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@chromium.org
, Oct 4 2017