New issue
Advanced search Search tips

Issue 807792 link

Starred by 1 user
Status: Fixed
Owner:
npm@chromium.org
Closed: Jan 15
Cc:
panicker@chromium.org
yoavweiss@chromium.org
npm@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

[Resource Timing] Chrome does not fire resourcetimingbufferfull properly

Project Member Reported by npm@chromium.org, Jan 31 2018 
Currently, Chrome fires resourcetimingbufferfull in two cases:
1. When after changing the size with setResourceTimingBufferSize, the buffer is full.
2. When a ResourceTiming entry is successfully added but the buffer is now full.

This does not match the spec (shouldn't fire on setResourceTimingBufferSize, and we are missing the buffer full flag).

Comment 1 by maxlg@chromium.org, May 16 2018 

"is now full" should be "the buffer is not full" in description?

ping as it's getting stale.

Comment 2 by npm@chromium.org, May 16 2018 

No, I do mean 'is now full'. resourcetimingbufferfull triggers when the buffer is full.

Comment 3 by dproy@chromium.org, Sep 4 

Ping: Any update here?

Comment 4 by npm@chromium.org, Sep 4 

The spec is being updated regarding how this event should be triggered. I'm not changing this until after the spec change is done.

Comment 5 by maxlg@chromium.org, Jan 15 

What's the status of the spec?

Comment 6 by yoavweiss@chromium.org, Jan 15

Status: Fixed (was: Assigned)
This was fixed in https://chromium-review.googlesource.com/c/chromium/src/+/1373819
Closing
►

Sign in to add a comment