roxleitan Reporter
	Description • 6 years ago

Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID:20180307220100

[Affected versions]:
Nightly 60.0a1, Firefox Beta 59.0b14

[Affected platforms]:
Ubuntu 16.04 X64, Mac OS X 10.12, Windows 10 x64

[Steps to reproduce]:
1.Launch Nightly 60.0a1 with a new profile
2.Login into https://calendar.google.com

[Expected result]:
The page should be loaded without issues

[Actual result]:
Two black lines are displayed when the page is loaded (please see the attached screenshot)

	Jeff Muizelaar [:jrmuizel]
	Comment 1 • 6 years ago

Can you still reproduce this?

	roxleitan Reporter
	Comment 2 • 6 years ago

Mozilla/5.0 (X11; Linux x86_64; rv:61.0) Gecko/20100101 Firefox/61.0
Build ID:20180411100123

I reproduced the issue using the latest Nightly 61.0a1 on Ubuntu 16.04 x64, Mac OS X 10.13 and Windows 10 x64.

	Jeff Muizelaar [:jrmuizel]
	Comment 3 • 6 years ago

Is it possible for you to get a regression window?

	roxleitan Reporter
	Comment 4 • 6 years ago

 Last good revision: 6cefe01ca7744d6ac3960c69eac833e2e65f7f8f (2017-02-17)
 First bad revision: d11c29c1db3a1bc96ad5792ebf8a89b2fbadcf85 (2017-02-18)
 Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=6cefe01ca7744d6ac3960c69eac833e2e65f7f8f&tochange=d11c29c1db3a1bc96ad5792ebf8a89b2fbadcf85

	Jeff Muizelaar [:jrmuizel]
	Comment 5 • 6 years ago

Is it possible to get an inbound/autoland range?

	roxleitan Reporter
	Comment 6 • 6 years ago

This is what mozregression displays:

CRITICAL: Last build d11c29c1db3a is missing, but mozregression can't find a build after - so it is excluded, but it could contain the regression!
There are no build artifacts on inbound for these changesets (they are probably too old).

	Jeff Muizelaar [:jrmuizel]
	Comment 7 • 6 years ago

I guess someone needs to do builds for this range to narrow it down.

	Ryan VanderMeulen [:RyanVM]
	Comment 8 • 6 years ago

I've never seen this personally. Roxana, this is still reproducible for you, I take it?

	roxleitan Reporter
	Comment 9 • 6 years ago

I cannot reproduce the issue on the latest Nightly 62.0a1(2018-06-25) and latest Beta 61.0b14.
But I could reproduce it on Firefox Release 60.0.2.

Since for Fx60 is wontfix, should I close this as WFM?

	Ryan VanderMeulen [:RyanVM]
	Comment 10 • 6 years ago

Makes sense, yeah.