1398477 - Google Cloud Platform shows blank page due to lack of Long Task implementation

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect, P3)

Description

[Ilja Nedilko]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20170909100226

Steps to reproduce:

Browse to https://console.cloud.google.com/ and login. Blank page is returned. Same issue on a clean install, two different clients. Works fine in beta, stable and other browsers.
Seems to have occurred after 2017-09-07 build.
Windows 10 Enterprise (and Professional, on another machine), both 1703 15063.540.


Actual results:

Blank page is displayed.


Expected results:

The page is displayed correctly.

Comment 1

[Alice0775 White]

setting dom.enable_performance_observe = false should fix.

This is not a recent regression in the nightly channel.
This is reproduced since Nightly49 (Bug 1271487).

And the prefs becomes true by default in next Beta57 (Bug 1386021).
So, it will be red alarm for next beta57.

Comment 2

[Alice0775 White]

[Tracking Requested - why for this release]: Google Cloud Platform is broken in Nightly57 and will be broken in next beta 57 cycle as well.

Comment 3

[Hiroyuki Ikezoe (:hiro)]

The site uses PerformanceObserver for observing long task [1], but we don't still support long task (bug 1348405).  Also, PerformanceObserver.observe() throws when no valid entry type is passed to the method.  Unfortunately when I implement PerformanceObserver long task api did not exist.  I think we can handle 'longtask' as a valid entry type, but the site should also work fine without long task support.

[1] https://w3c.github.io/longtasks/

Comment 4

[Hiroyuki Ikezoe (:hiro)]

I think this is a sort of web compact issue.  WebKit does not handle 'longtask' as a valid entry type either [1], so the Google Cloud Platform will not work on WebKit either. I think the site should work even though PerformanceObserver.observe() throws an exception. :overholt, what should we do for such cases? 

FWIW here is a try that handles 'longtask' as a valid entry, it makes the Google Cloud Platform work.

Also note that there are some discussions about APIs to get information what entry types are supported by UA [2][3].

https://treeherder.mozilla.org/#/jobs?repo=try&revision=8ff2d59a74e2f16d90133993f580c434b08c8a02

[1] https://trac.webkit.org/browser/webkit/trunk/Source/WebCore/page/PerformanceEntry.cpp?rev=211406#L53
[2] https://github.com/w3c/performance-timeline/issues/77
[3] https://github.com/w3c/performance-timeline/issues/64

Comment 5

[Pascal Chevrel:pascalc (PTO until April 26)]

Also reported at https://github.com/webcompat/web-bugs/issues/9716

Comment 6

[Julien Cristau [:jcristau]]

Tracking as upcoming webcompat regression in 57 beta.

Comment 7

[Ilya Grigorik]

Opened spec issue to track this: https://github.com/w3c/performance-timeline/issues/87 -- would appreciate any feedback.

Comment 8

[Julien Cristau [:jcristau]]

Per https://github.com/webcompat/web-bugs/issues/9716#issuecomment-328915490 this will be fixed on google cloud platform within a week.

Comment 9

[Dane MacMillan [:danemacmillan]]

I experience the same issue in Nightly.

Comment 10

[Andrew Overholt [:overholt]]

(In reply to Hiroyuki Ikezoe (:hiro) from comment #4)
> I think this is a sort of web compact issue.  WebKit does not handle
> 'longtask' as a valid entry type either [1], so the Google Cloud Platform
> will not work on WebKit either. I think the site should work even though
> PerformanceObserver.observe() throws an exception. :overholt, what should we
> do for such cases? 

The spec discussion is probably the best place for this and I'm happy to hear Google Cloud Platform will work without a potentially ugly fix here.

Comment 11

[Ekanan Ketunuti]

it's fixed.