theguardian.com glitchy media
Categories
(Core :: Widget: Gtk, defect)
Tracking
()
People
(Reporter: jnqnfe, Unassigned)
Details
Attachments
(4 files)
Screenshot from firefox 130
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:130.0) Gecko/20100101 Firefox/130.0
Steps to reproduce:
I've just upgraded to firefox 130.0-1 on my laptop via the Debian Sid repository. Having done so I've found that most media elements on theguardian.com are now glitchy and unviewable. The only ones unaffected seem to be embedded SVG. This problem was not present yesterday under 129.0.2-1, and is not there with firefox-esr 115.15.0esr-1. I've also not noticed any such problems on various other websites. It's not just the guardian homepage but affects articles too.
Actual results:
I've attached a screenshot saved from firefox. In this saved screenshot all of the broken media elements have been captured as either black rectangles or transparent rectangles. The black rectangles are exactly what is shown in the 'live' view of the page. The transparent ones show wildly flickering and repeated fragments of content. This content is initially from the page, but if I switch away to a different tab/window/program and back again they show content from the other tab/window/program as though those portions of the screen have not been redrawn, though revert to flickering fragmented content from the page upon scrolling.
Added a few 'visible content' screenshots for comparison saved from firefox-esr 115.15.0 (couldn't save the full page, it just fails due to size).
|
||
Comment 4•6 months ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Fixed as of version 130.0-2. Going to resolve as duplicated of 1916038.
|
||
Comment 6•6 months ago
|
||
(In reply to Lyndon from comment #0)
The only ones unaffected seem to be embedded SVG.
If the issue was svg's then I wouldn't have expected bug 1916038 to have an effect. From the screenshot though it looks like it was not svgs, so then bug 1916038 would make sense.
Description
•