[Preconditions]:

• Reproducible only with MacBook Pro (13-inch, 2017)

[Affected versions]:

• 68.0a1 (20190516215643)
• 68.0b2 Dev Edition(20190516152822)
• 67.0 (20190516215225)

[Affected platforms]:

• macOS 10.14.3

[Steps to reproduce]:

1. Go to https://www.aliexpress.com/
2. Click on the Sign in button

[Expected result]:

• The login form is visible

[Actual result]:

• The login form is not visible

[Regression range]:

• Reproducible on Fx 61.0a1. I will provide more information asap.

[Additional Notes]:

• This issue is not reproducible:
  • with MacBook Pro (Retina, 13-inch, early 2015) or MacBook Air
  • with the same MacBook from Preconditions on macOS 10.13.6
  • with the same MacBook from Preconditions on Chrome
• Note that if I try to take a screenshot using Shift+Command+4 the login form is visible (see screencast)
• The login form is functional.

This issue is not a regression, reproducible way back to Fx 31.0a1.

@Anca: Is this still reproducible? It looks like the design of the sign in form has since changed on https://www.aliexpress.com

I have a 13-inch MacBook Pro (2018) and haven't been able to reproduce on there.

This issue is still reproducible on my side, on both latest Beta 68.0b4 and latest Nightly (2019-05-26), but indeed there is a bit of improvement, this time the login form is perceivable - see screenshot. Note that I only have two MacBooks available, and like I’ve mentioned above, issue is reproducible only with MacBook Pro (13-inch, 2017), but not with MacBook Pro (Retina, 13-inch, early 2015).

The priority flag is not set for this bug.
:dbaron, could you have a look please?

For more information, please visit auto_nag documentation.

I think the fact that the screenshot tool makes this show up indicates that this is some sort of graphics bug, so I should let them prioritize.

The contents of the Graphics section of about:support on the one machine where you see the problem might help figuring out how to reproduce the problem.

Here is the content from about:support for the latest Beta build (68.0b7) from the machine where this issue is reproducible: https://pastebin.com/PBeUFegm