Open Bug 1724663 Opened 3 years ago Updated 8 months ago

YouTube videos glitch out on the bottom half when when privacy.resistFingerprinting is enabled

Categories

(Core :: DOM: Security, defect, P3)

Firefox 90
Unspecified
Linux
defect

Tracking

()

People

(Reporter: yoasif, Unassigned)

References

(Blocks 1 open bug)

Details

(Whiteboard: [domsecurity-backlog1])

Attachments

(3 files)

Attached image image.png

From https://www.reddit.com/r/firefox/comments/p0tryk/youtube_videos_glitch_out_on_the_bottom_half/

Happens on any youtube video, any.

I just noticed that the glitch is part of the youtube overaly (the one with the playback controls and such). Playing the video and then waiting a few seconds for it to go away works fine.

See screenshot.

Video: https://streamable.com/7efdj2

Disabling HW WebRender doesn't change anything.

User confirms that this is solved when when privacy.resistFingerprinting is disabled.

Attached file about:support
Summary: YouTube videos glitch out on the bottom half (AMD Radeon(TM) Vega 11 Graphics) → YouTube videos glitch out on the bottom half when when privacy.resistFingerprinting is enabled
Component: Graphics: WebRender → DOM: Security

Thanks for this. This is consistent with the randomized canvas rendering we did. Hopefully we will soon get software rendering with canvas working and can do away with all the canvas annoyances.

Severity: -- → S4
Priority: -- → P3
Whiteboard: [domsecurity-backlog1]
Attached image 2022-09-06_00-25.png

Operating System: Fedora Linux 36
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.97.0
Qt Version: 5.15.5
Kernel Version: 5.19.6-200.fc36.x86_64 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-2400 CPU @ 3.10GHz
Memory: 15,6 GiB of RAM
Graphics Processor: AMD OLAND

Firefox install method: Flathub

A comment on why anyone would like to enable this config in the first place: Oddly, pressing <kbd>F</kbd> does not make the video fullscreen in Firefox while it does in Chrome.

This page suggests to do it in order to get it working.

I still have this bug in Firefox 122.0.1, the bug is still present when full screening, and setting privacy.resistFingerprinting to false resolves the issue, however, I do not see that as a suitable long-term solution.

and re-enabling it after I disabled it to test has resolved the issue??

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: