1915589 - fanczs.com - The page does not load

Status: NEW

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

Description

[Raul Bucata]

Environment:
Operating system: Windows 10
Firefox version: Firefox 129.0.1 (release)

Preconditions:

• Clean profile

Steps to reproduce:

1. Navigate to: https://mmo.fanczs.com/scs/home
2. Observe

Expected Behavior:
The page loads

Actual Behavior:
Blank page

Notes:

• Reproducible on the latest Firefox Release and Nightly
• Reproducible regardless of the ETP setting
• Works as expected using Chrome

---

Created from webcompat-user-report:f724d713-6718-462b-93a4-c4a59009b746

Comment 1

[Ksenia Berezina [:ksenia]]

Seeing this error in the console:

Uncaught TypeError: PerformanceObserver.observe: Can't call observe with both `type` and `entryTypes`

Comment 2

[Jeff Muizelaar [:jrmuizel]]

The call to observe looks like: .observe({entryTypes:["resource"],buffered:!0} which the spec says should throw a TypeError. https://w3c.github.io/performance-timeline/#observe-method

We should check if Chrome throws an exception in this case.

Comment 3

[Jeff Muizelaar [:jrmuizel]]

Attachment: Reduced test case

Chrome and Safari both don't throw on this test case. We should either update the spec and implementation or get Chrome and Safari to fix theirs.

Comment 4

[Jeff Muizelaar [:jrmuizel]]

Hiro, thoughts on what we should do here?

Comment 5

[Hiroyuki Ikezoe (:hiro)]

The buffered argument was added after I implemented the initial v1 spec, so I didn't know about it at all, thus I learned the background.

From what I can tell is the best thing we can do here is to reach out the web site author and ask to stop calling observe() both with entryTypes and buffered.

There's a chromium bug that they have been struggling to change their behavior to throw an exception. It looks to me they've waited for a state where the incorrect usage drops, I am not sure what the threshold of the usage percentage is.

CCing npm@chromium who wrote the spec change for the buffered support.