Skip to content

Conversation

@patrickhulce
Copy link
Collaborator

@patrickhulce patrickhulce commented May 23, 2021

Summary
Buffered flag only works when you use type not, entryTypes. It's not really a regression when we turned it on, because we just fell back to the same behavior as before we added it a few weeks ago, but this will make the fix actually work :) (we never really needed buffered either, mostly an extra boost of wait condition correctness in ultrarare cases where entries weren't emitted fast enough)

Related Issues/PRs
fixes #12544

@patrickhulce patrickhulce requested a review from a team as a code owner May 23, 2021 00:57
@patrickhulce patrickhulce requested review from connorjclark and removed request for a team May 23, 2021 00:57
@google-cla google-cla bot added the cla: yes label May 23, 2021
Copy link
Collaborator

@connorjclark connorjclark left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Buffered flag only works when you use type not, entryTypes.

wut

@paulirish
Copy link
Member

Buffered flag only works when you use type not, entryTypes.

wut

yup. super subtle thing with the PO. if you wanna use buffered:true you can only specifiy a single type and not multiple entryTypes. I think the docs now are slightly better about this than they were months ago.

@paulirish
Copy link
Member

paulirish commented May 25, 2021

The console was emitting a warning when we were running this, but we weren't listening for any messages…

image

edit: AH, that's what tipped us off. phew.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

PerformanceObserver warning issued during audit

4 participants