Summary: | PerformanceObserver should work with {type: 'paint', buffered: true } | ||
---|---|---|---|
Product: | WebKit | Reporter: | Andrew Scheuermann <andrewscheuermann> |
Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | bfulgham, noam, simon.fraser, webkit-bug-importer, wilander |
Priority: | P2 | Keywords: | BrowserCompat, InRadar |
Version: | Safari 15 | ||
Hardware: | Unspecified | ||
OS: | Unspecified |
Description
Andrew Scheuermann
2022-02-04 13:32:41 PST
*** This bug has been marked as a duplicate of bug 78011 *** Not a dup. This is already covered in a web platform test: https://wpt.live/paint-timing/fcp-only/fcp-iframe.html From what I checked it works as expected in safari. I also tested it manually in a fresh page. Note that the observer needs to be added before the paint happens - in your example steps that's not the case. Can you post a test page where you add an observer before the paint and the observer is not called? To clarify, the "Steps to reproduce" show a PerformanceObserver that is created with {type: 'paint', buffered: true}. The presence of the buffered parameter means that the PerformanceObserver callback should invoke with paint entries that occurred ~before~ the observer is added. You can reproduce this buffered behavior on Chrome, Firefox, Opera, and Edge by copying in the code at any time after the initial paint occurs. I've updated the bug description to "PerformanceObserver should work with {type: 'paint', buffered: true }" https://developer.mozilla.org/en-US/docs/Web/API/PerformanceObserver/observe#parameters (In reply to Andrew Scheuermann from comment #5) > To clarify, the "Steps to reproduce" show a PerformanceObserver that is > created with {type: 'paint', buffered: true}. The presence of the buffered > parameter means that the PerformanceObserver callback should invoke with > paint entries that occurred ~before~ the observer is added. > > You can reproduce this buffered behavior on Chrome, Firefox, Opera, and Edge > by copying in the code at any time after the initial paint occurs. > > > I've updated the bug description to "PerformanceObserver should work with > {type: 'paint', buffered: true }" > > https://developer.mozilla.org/en-US/docs/Web/API/PerformanceObserver/ > observe#parameters Ah. I think this is a dup of https://bugs.webkit.org/show_bug.cgi?id=225305 *** This bug has been marked as a duplicate of bug 225305 *** I marked it as dup, and found an existing failing WPT for this https://wpt.fyi/results/paint-timing/fcp-only/buffered-flag.window.html?label=experimental&label=master&aligned which would make it easier to reproduce and fix. |