1804240 - Glitches on element from https://connect-homes.com/developers

Status: NEW

(Core :: Layout: Images, Video, and HTML Frames, defect, P3)

Description

[Bogdan Maris, Desktop Test Engineering]

Found in

• Firefox 108.0

Affected versions

• Firefox 108.0
• Latest Nightly 109.0a1
• Firefox 73.0

Tested platforms

• Affected platforms: Windows 10 64bit, macOS 11.6, Ubuntu 22.04
• Unaffected platforms: none

Preconditions

• none

Steps to reproduce

1. Open https://connect-homes.com/developers
2. Scroll until reaching the element from "THE MODERN BUILDING BLOCKS FOR DEVELOPMENT"

Expected result

• The image animation is correctly displayed

Actual result

• The animation glitches

Regression range

• Not a recent regression since Firefox 73 is also affected, will try and find if this is a regression at all.

Additional notes

• Not sure if this is the correct component for this issue, please change it if it belongs somewhere else.
• The screenshare I made with the issue is too large and I could not upload it directly here so I uploaded it in Gdrive: https://drive.google.com/file/d/1xo8nRPvfeUYhiaLwFUsFrVTQ2Ah9Bhbh/view?usp=sharing

Comment 1

[Bogdan Maris, Desktop Test Engineering]

(In reply to Bogdan Maris [:bogdan_maris], Release Desktop QA from comment #0)

Regression range

• Not a recent regression since Firefox 73 is also affected, will try and find if this is a regression at all.

Apparently the first "bad" build I can find is from 2019-08-22, the one from 21st does not show the content of the page. I will say this is not a regression based on this but if the reason is found and it turns out that this is indeed a regression (though a very old one) please add the 'regression' field inside keywords field.

Comment 2

[Timothy Nikkel (:tnikkel)]

This looks like toggling display none on image elements and expecting sync decoding.

Comment 3

[Andrei Vaida [:avaida]]

Desktop QA has been highlighting this defect as a known issue for several release cycles now, following regression testing. Emilio, it would really help us if you set a priority on this bug — it will give us clarity on whether this issue is still worth mentioning in future test reports.

Comment 4

[Emilio Cobos Álvarez (:emilio)]

Tim, it seems this might be worth trying to address somehow? Maybe forcing sync-decoding of data: URIs? But other than something like that, it seems the right thing to do would be for the page to specify decoding='sync'.

However, even with that (well, a local build with always-sync-decode) we seem to glitch somehow.