Closed Bug 1276923 Opened 4 years ago Closed 4 years ago
White artifacts and flickering when scrolling on Vimeo videos
[Affected versions]: - latest Nightly 49.0a1 [Affected platforms]: - Windows 10 x64 - Ubuntu 16.04 LTS x64 [Steps to reproduce]: 1. Launch Firefox 2. Go to www.vimeo.com 3. Play a video - https://vimeo.com/167414855 - https://vimeo.com/40805886 4. Scroll down/up [Expected result]: - Video is properly displayed. [Actual result]: - White artifacts/flicker present. [Regression range]: - Last good revision: 132e391ed5e588241227dfb48083dcd57ac3142f - First bad revision: 9542a06550b6c6e8ca512e705d9e3732036928a5 - Pushlog: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=132e391ed5e588241227dfb48083dcd57ac3142f&tochange=9542a06550b6c6e8ca512e705d9e3732036928a5 [Additional notes]: - Screencast attached. - Not reproducible with layers.async-pan-zoom.enabled → false nor with e10s disabled, - Unable to reproduce under Mac OS X 10.10.5
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/622c7afef4ae Disable ssse3 scaler until it's fixed
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/724b9cdd239f Actually disable ssse3 scaler until it's fixed. r=mstange
This actually works
Comment on attachment 8759766 [details] [diff] [review] More properly transform the clip Review of attachment 8759766 [details] [diff] [review]: ----------------------------------------------------------------- Ah, this makes a lot of sense. We push the clip on the buffer while it has the original transform, and then we overwrite the transform with something else. But the fast path operates in device space and ignores the existing clip on the buffer, so we need to know the original clip at the original transform. Maybe call transformedClipRect bufferDeviceClip? Up to you.
Attachment #8759766 - Flags: review?(mstange) → review+
Pushed by email@example.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/49762b7df747 BasicCompositor: Properly transform the clip. r=mstange
This issue is verified fixed on 49.0b7 (2016-08-25), using Windows 10 x64 and Ubuntu 16.04 LTS x64. I will mark this bug accordingly.
You need to log in before you can comment on or make changes to this bug.