-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<img> setting src = "" should maybe be sync #2429
Comments
Result in Edge 13 for 4936:
|
Gecko now always sync loads image for non-responsive case (without |
It sounds like we should not necessarily blindly follow the current specification, though. |
Yeah this a case I probably did not carefully consider before. Though given WebKit's behavior it may not be critical for Web compat either way. But it seems slightly safer to align with majority behavior (in the non-responsive case). |
I see, I will also handle this case in https://bugzilla.mozilla.org/show_bug.cgi?id=1076583. Thank you, @zcorpan and @jdm. |
Per #4884 (comment), it looks like browsers have different behavior not only in non-responsive case, but also responsive case. :( |
I was told webkit has still async behavior here. @rniwa do you think webkit would be will to follow Gecko's and Blink's behavior here? |
Note that this is more subtle than just |
https://html.spec.whatwg.org/#updating-the-image-data
From web-platform-tests/wpt#5060
See http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4936
It seems that in Chromium and Gecko this case is sync (doesn't await a stable state).
With
picture
: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4937Chromium: still sync. Gecko awaits a stable state. Per spec updates shouldn't be sync if
srcset
orpicture
are used.WebKit seems a bit weird for the case of setting
src
to empty string or removing thesrc
attribute doesn't change.width
or the rendered dimensions but it doesn't render the old image.The text was updated successfully, but these errors were encountered: