You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the expected behavior:
Web pages with this pattern appear to expect the data-src to "win".
I think lazySizes could remove loading attributes on iframes with a lazyload class so that the placeholder src is loaded eagerly and to avoid timing issues with which navigation is the last one, in current Firefox and Safari. Or at least remove loading attribute right before location.replace.
What happened instead:
In Firefox and Safari (maybe subject to timing), the location.replace() navigation happens first and then the browser lazy-loads the src URL.
In what environment (browser/device etc.) does this bug happen/not happen:
Firefox, Safari: yes
Chrome: no
Keywords help others to find this issue:
The text was updated successfully, but these errors were encountered:
Describe the bug
Using lazySizes with
iframe
and a placeholdersrc
andloading=lazy
makes the placeholdersrc
win.Also see whatwg/html#10213
Possibly related: #705 , #927
To Reproduce
https://software.hixie.ch/utilities/js/live-dom-viewer/saved/12475
Steps to reproduce the behavior:
What is the expected behavior:
Web pages with this pattern appear to expect the
data-src
to "win".I think lazySizes could remove
loading
attributes on iframes with alazyload
class so that the placeholdersrc
is loaded eagerly and to avoid timing issues with which navigation is the last one, in current Firefox and Safari. Or at least removeloading
attribute right beforelocation.replace
.What happened instead:
In Firefox and Safari (maybe subject to timing), the
location.replace()
navigation happens first and then the browser lazy-loads thesrc
URL.In what environment (browser/device etc.) does this bug happen/not happen:
Firefox, Safari: yes
Chrome: no
Keywords help others to find this issue:
The text was updated successfully, but these errors were encountered: