[Affected versions]:

• 67.0.1
• 68.0b6
• 69.0a1 (2019-05-29)

[Affected platforms]:

• Windows 7 x64

[Steps to reproduce]:

1. Login with valid credentials on https://www.linkedin.com/
2. Observe any button with blue background (eg “Keep connecting”) inside the starting steps header.

[Expected result]:

• No glitches occur.

[Actual result]:

• Visual glitches are triggered.

[Regression range]:

• Reproducible on Fx 65.0a1, but not on Fx 61.0a1. I will provide more info asap.

[Additional Notes]:

• This issue is not reproducible on Chrome.
• Setting the layers.acceleration.disabled on True fixes the issue.
• GPU: Intel HD Graphics 5500

Can you attach your about:support? Also can you reproduce this on the latest nightly build? Thanks!

Here is the content from about:support - https://pastebin.com/f8CjehDa

(In reply to Andrew Osmond [:aosmond] from comment #1)

...can you reproduce this on the latest nightly build?

Yes, it is reproducible with the latest Nightly (20190530094559).

I've managed to determine a regression range:

• Last good revision: 315103f6db6b1f44647d82c0f494c2d45fc42e07
• First bad revision: 90c347a61bd56af575c2c812bac026e7ead65de2
• Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=315103f6db6b1f44647d82c0f494c2d45fc42e07&tochange=90c347a61bd56af575c2c812bac026e7ead65de2
• Potential regressor: Bug 1474466

Hi Matt,

It seems that mozregression pointed out Bug 1474466 for causing this regression.

Can you please have a look?

Thanks!

Can you please post the graphics section from about:support.

This looks like a Direct2D bug. We could back the patch out, but it was a pretty big performance win on MotionMark iirc.

Happy to take a patch for 70 but since this is triaged and set to P3 priority I'm setting it as fix-optional.
That will remove the bug from weekly regression triage.