1439257 - Clipping of video on Facebook is broken

Status: RESOLVED FIXED

(Core :: Graphics: WebRender, defect, P1)

Description

[Jeff Muizelaar [:jrmuizel]]

Attachment: out.png

See attached screenshot

Comment 1

[Darkspirit]

login and open https://www.facebook.com/search/str/Firefox/keywords_search

try builds from bug 1437572:
> WR @ 38df48c62c929a3603f3c6e6393c2be8f1c88903
mozregression --repo try --launch 064776f7e05b066c4ad40181ba397b751dcfd477 --pref gfx.webrender.all:true startup.homepage_welcome_url:"https://www.facebook.com/"
good

> WR @ d69bd28a055e2afb2ad234eea297dd45f9b4b4e5
mozregression --repo try --launch 51cf20720ce738e9a9bb1a1b65ec4a2efb797f69 --pref gfx.webrender.all:true startup.homepage_welcome_url:"https://www.facebook.com/"
bad

Regression range: https://github.com/servo/webrender/compare/38df48c62c929a3603f3c6e6393c2be8f1c88903...d69bd28a055e2afb2ad234eea297dd45f9b4b4e5

Comment 3

[Darkspirit]

Fixed by https://github.com/servo/webrender/pull/2477.
Confirmed in https://github.com/servo/webrender/issues/2438#issuecomment-369240390.

Comment 4

[Darkspirit]

Verified fixed in Nightly 60 x64 20180302104326 de_DE b2a9a4bb5c94de179ae7a3f52fde58c0e2897498 @ Debian Testing. Thanks!

Comment 5

[Asif Youssuff]

Attachment: Peek 2018-03-02 13-01.webm

Still happening on my machine (see screencast):

mozregression --repo try --launch b2a9a4bb5c94de179ae7a3f52fde58c0e2897498 --pref gfx.webrender.all:true

Comment 6

[Glenn Watson [:gw]]

Is this now a Linux + Sandybridge specific issue, like https://bugzilla.mozilla.org/show_bug.cgi?id=1440179 ?

Comment 7

[Darkspirit]

(In reply to Glenn Watson [:gw] from comment #6)
> Is this now a Linux + Sandybridge specific issue, like
> https://bugzilla.mozilla.org/show_bug.cgi?id=1440179 ?

Yes, I noted that in https://github.com/servo/webrender/issues/2438. One spin-off bug about this would have been cleaner.

Comment 8

[Darkspirit]

> One spin-off bug about this would have been cleaner.

Now I duped all the Intel Sandybridge bugs over to bug 1441025 to have only one bug about this potential driver issue.
For all other devices (so far): Verified fixed in comment 4.