Image loading is asynchronous when 'src' is set to a data URL.
Reported by
andre.mi...@gmail.com,
Mar 15 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.98 Safari/537.36 Steps to reproduce the problem: 1. Open attached html file in Chrome 57 2. Refresh several times. The outcome is not predictable. 3. Try in Chrome 56 where it works every time. What is the expected behavior? toDataURL should immediately transfer all pixel data synchronous to the image. What went wrong? toDataURL acts now a-synchronous. Did this work before? Yes 56 Chrome version: 57.0.2987.98 Channel: stable OS Version: OS X 10.12.3 Flash Version: Shockwave Flash 25.0 r0 Any workaround is welcome as well. I think it is reasonable to have toDataURL being a-synchronous (to allow responsive dealing with large images) but there should be a way to transfer all pixel data immediately.
,
Mar 16 2017
,
Mar 20 2017
Able to reproduce the issue on Mac 10.12.3, Win 10 and Ubuntu 14.04 using 57.0.2987.98, 57.0.2987.110 and canary 59.0.3046.0. Bisect info: ============ Good: 57.0.2970.0 Bad : 57.0.2971.0 https://chromium.googlesource.com/chromium/src/+log/1aa292f37d0556e36624e9968db50f39a5523a07..b6403174c6111ea0947dc7cf8b1eb8a6f9e8546c Review-Url: https://codereview.chromium.org/2592113003 yoav: Could you please take a look into this if its related to your change.
,
Mar 20 2017
Re-triaging ans re-naming bug. The bug is not with toDataURL, is is with image loading. Loading is expected to be synchronous when img.src is set to a value that is a data URL.
,
Mar 21 2017
The spec disagrees that data URL images should be loaded synchronously. Chrome was the only browser to load them synchronously and that was fixed in https://bugs.chromium.org/p/chromium/issues/detail?id=514206 |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by nyerramilli@chromium.org
, Mar 16 2017