1405276 - [Ubuntu] Graphical issues on Youtube

Status: RESOLVED DUPLICATE of bug 1404323

(Core :: Graphics, defect)

Description

[Iulia Cristescu, QA [:JuliaC] (away, please needinfo? [e-mail])]

[Affected versions]:
- 57.0b5 build1 (20171002181526)
- deved57.0b3 build1 (20170925150345)

[Affected platforms]:
- Ubuntu 14.04 x86/64
- Ubuntu 12.04 x86/64

[Steps to reproduce]:
1. Launch Firefox
2. Navigate to https://www.youtube.com/, choose a random video and play it
3. Inspect the Settings site menu 
4. Search a random word in the Youtube search box and inspect the drop down results list

[Expected result]:
- The video is properly rendered
- No graphical issues are triggered

[Actual result]:
- Video glitches can be noticed in the Settings site menu and in the drop down search results list (see the screencast for more details https://goo.gl/SCTMYE)

[Regression range]:
- The issue is reproducible starting with deved57.0b3 build1 (20170925150345)
- It seems to be triggered by bug 1397918

[Additional notes]:
- Ubuntu 16.04 is not affected

Comment 2

[Ethan Tseng [:ethan]]

Hi Lee,

Could you confirm this bug is a duplicate of bug 1404323?
The tracking flags in these two bugs are not consistent, which made us confused.

Comment 3

[Lee Salzman [:lsalzman]]

(In reply to Ethan Tseng [:ethan] - 57 Regression Engineering Support from comment #2)
> Hi Lee,
> 
> Could you confirm this bug is a duplicate of bug 1404323?
> The tracking flags in these two bugs are not consistent, which made us
> confused.

It is a duplicate of bug 1404323.

Comment 4

[Ethan Tseng [:ethan]]

(In reply to Lee Salzman [:lsalzman] from comment #3)
> It is a duplicate of bug 1404323.

Thanks for the confirmation.
I don't doubt your judgment, but could you please shed some light on the differences of the tracking flags?

This bug:
firefox56	---	unaffected
firefox57	---	affected
firefox58	---	unaffected

Bug 1404323:
firefox56	---	wontfix
firefox57	+	fixed
firefox58	---	fixed

The flags in this bug indicate it is a new regression for 57, while the ones in bug 1404323 explain differently.
Maybe some of the flags were set mistakenly?  Or there's some complication?

Comment 5

[Lee Salzman [:lsalzman]]

(In reply to Ethan Tseng [:ethan] - 57 Regression Engineering Support from comment #4)
> (In reply to Lee Salzman [:lsalzman] from comment #3)
> > It is a duplicate of bug 1404323.
> 
> Thanks for the confirmation.
> I don't doubt your judgment, but could you please shed some light on the
> differences of the tracking flags?
> 
> This bug:
> firefox56	---	unaffected
> firefox57	---	affected
> firefox58	---	unaffected
> 
> Bug 1404323:
> firefox56	---	wontfix
> firefox57	+	fixed
> firefox58	---	fixed
> 
> The flags in this bug indicate it is a new regression for 57, while the ones
> in bug 1404323 explain differently.
> Maybe some of the flags were set mistakenly?  Or there's some complication?

I was not aware we had to go back and update every status flag on what is just a duplicate bug? That seems a lot of duplicate busy work. These bug threads are about the exact same cause, so, no, there is no underlying motive here for why the status flags are different, other than that I thought this bug was retired as a duplicate and so we're done modifying it?