Open
Bug 1420913
Opened 8 years ago
Updated 1 year ago
consider notifying PerformanceObserver using idle dispatch
Categories
(Core :: DOM: Performance APIs, enhancement, P3)
Tracking
()
NEW
People
(Reporter: bkelly, Unassigned)
References
Details
Apparently the PerformanceObserver spec says that events should be dispatched at low priority during idle times. No browser does this yet, though. Chrome is thinking of doing it:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/TgoXNRtA3Zs
We should consider it as well.
Valentin, Andrea, what do you think?
Flags: needinfo?(valentin.gosu)
Flags: needinfo?(amarchesini)
Reporter | ||
Comment 1•8 years ago
|
||
Note, I think changing this would mainly involve changing this:
https://searchfox.org/mozilla-central/source/dom/performance/Performance.cpp#518
To use NS_IdleDispatchToCurrentThread().
Comment 2•8 years ago
|
||
Andrea has more of an insight into PerformanceObserver behaviour, but this sounds like a reasonable change to me.
Flags: needinfo?(valentin.gosu)
Reporter | ||
Comment 3•8 years ago
|
||
I think the main concern I have is if sites are depending on the timing somehow. The blink-dev thread has some discussion of that.
Comment 4•8 years ago
|
||
(In reply to Ben Kelly [:bkelly] from comment #3)
> I think the main concern I have is if sites are depending on the timing
> somehow. The blink-dev thread has some discussion of that.
It seems that the discussion is suspended waiting for takeRecords(). We should implement takeRecords() as well, btw. /me filing a bug.
Flags: needinfo?(amarchesini)
Updated•8 years ago
|
Priority: -- → P3
Assignee | ||
Updated•6 years ago
|
Component: DOM → DOM: Core & HTML
Updated•3 years ago
|
Severity: normal → S3
Updated•1 year ago
|
Component: DOM: Core & HTML → DOM: Performance
You need to log in
before you can comment on or make changes to this bug.
Description
•