webpage at gog.com broken assets with nightly 92.0a1 on Debian stable amd64
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr78 | --- | unaffected |
firefox90 | --- | unaffected |
firefox91 | --- | unaffected |
firefox92 | + | verified |
People
(Reporter: dclarke, Assigned: emilio)
References
(Regression, )
Details
(Keywords: regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:92.0) Gecko/20100101 Firefox/92.0
Steps to reproduce:
try to view url : https://www.gog.com/games?system=lin_mint%2Clin_ubuntu&sort=popularity&page=1
Actual results:
Many assets on the page do not load.
Expected results:
Page should have loaded as per usual on Edge and Chrome etc. To be honest I had someone else test the page with Edge. I have reports that the url works "Works on Chromium" and also "Brave" which is some strange browser on windows.
Comment 1•3 years ago
|
||
I can reproduce the issue in nightly92.0a1 Windows10.
Images are no longer displayed.
Comment 2•3 years ago
|
||
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=911545677d2bb4f8b019eb0fdf2b421988419ee6&tochange=7a6b0696b90cdf48a4f19d7d997e4bbac79d1160
Assignee | ||
Comment 3•3 years ago
|
||
Wow, they rely on <source>
being displayed to lazy-load stuff and then unhide the image... Amazing.
Assignee | ||
Comment 4•3 years ago
|
||
[Tracking Requested - why for this release]: Regression on a broken page that makes Firefox feel broken. We should fix this before releasing, but I want to try outreach first as described in the HTML spec issue.
Ok, it seems they don't use any off-the-shelf lazy-loading solution, which was my fear (if they did, then all bets are off the table). I filed https://github.com/whatwg/html/issues/6886 to discuss this.
Updated•3 years ago
|
Updated•3 years ago
|
Comment 5•3 years ago
|
||
The probably very popular german news site https://www.tagesschau.de (including subpages) is also affected/broken.
Updated•3 years ago
|
Assignee | ||
Comment 6•3 years ago
|
||
Making <source> display: none is not web compatible. <track> could
probably stay, your call, but other browsers also don't do this so
perhaps we should just change the spec...
Assignee | ||
Updated•3 years ago
|
Comment 9•3 years ago
|
||
bugherder |
Updated•3 years ago
|
Comment 11•3 years ago
|
||
I've reproduced this issue on Windows 10x64, using an affected Nightly version 92.0a1 (2021-07-20).
Verified fixed with Firefox 92.0b2 (20210810185524) on Windows 10x64, macOS 10.13 and Ubuntu 20.04.
Description
•