Closed Bug 1667836 Opened 1 year ago Closed 7 months ago

Prototype PerformanceEventTiming

Categories

(Core :: Performance, enhancement, P3)

enhancement

Tracking

()

RESOLVED FIXED
87 Branch
Tracking Status
firefox87 --- fixed

People

(Reporter: sefeng, Assigned: sefeng)

References

(Depends on 1 open bug)

Details

Attachments

(9 files)

We are interested in prototyping PerformanceEventTiming. This bug intends to get two things done.

  1. The basic setup for PerformanceEventTiming, such as webidl and integration with performance observer etc.

  2. Making keydown event is available for PerformanceEventTiming.

Flags: needinfo?(sefeng)

Hi Sean - could you set the priority and severity for this bug? It's showing up in the triage bucket. I understand you are planning on working on it too so if you could assign it to yourself that would be great. thank you!

Assignee: nobody → sefeng
Severity: -- → S3
Flags: needinfo?(sefeng)
Priority: -- → P3
Depends on: 1674783
Depends on: 1680266

According to https://w3c.github.io/timing-entrytypes-registry/#registry,
unlike other performance entries, event and first-input entries have
their own algorithms to determine whether it can be added to observers.
This patch factors some code to allow such algorithms can be
implemented.

PerformanceEventTiming is an new API that we'd like to expose to the
web. This is mainly for supporting Google's Web Vital stuff to
grant more transparency to Google's search algorithm.

Spec: https://wicg.github.io/event-timing/#sec-performance-event-timing

Depends on D102034

Performance event entries should only be retrieved by
PerformanceObserver, so it can't be retrieved by using
Performance.GetEntries* APIs.

Depends on D102035

This interface is part of PerformanceEventTiming.

Spec: https://wicg.github.io/event-timing/#sec-event-counts

Depends on D102036

Depends on D102038

Attachment #9197490 - Attachment description: Bug 1667836 - Fix some bugs in PerformanceEventTiming WPT tests → Bug 1667836 - Fix some bugs in PerformanceEventTiming related tests
Attachment #9197487 - Attachment description: Bug 1667836 - Implement PerformanceEventTiming → Bug 1667836 - Implement PerformanceEventTiming Interface
Attachment #9201256 - Attachment description: Bug 1667836 - Add a event-timing test to ensure target is set to null for shadow DOM r=smaug → Bug 1667836 - Add an event-timing test to ensure target is set to null for shadow DOM r=smaug
Pushed by sefeng@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/ee8916455d0b
Make performance entries may have different `should add entry` algorithm r=smaug
https://hg.mozilla.org/integration/autoland/rev/c44b8a99085c
Use nsAtom for entry comparison in GetEntriesByType r=smaug
https://hg.mozilla.org/integration/autoland/rev/847dc068bb98
Add CC support to LinkedList r=smaug
https://hg.mozilla.org/integration/autoland/rev/e86df3d99d16
Implement PerformanceEventTiming Interface r=smaug
https://hg.mozilla.org/integration/autoland/rev/a9ab8d398b4d
Add an event-timing test to ensure target is set to null for shadow DOM r=smaug
https://hg.mozilla.org/integration/autoland/rev/2312a6f7ead7
Allow performance event entries can only be retrieved by PerformanceObserver r=smaug
https://hg.mozilla.org/integration/autoland/rev/2e7570ebeca3
Implement EventCounts Interface r=smaug
https://hg.mozilla.org/integration/autoland/rev/9776e21232ef
Fix some bugs in PerformanceEventTiming related tests r=smaug
https://hg.mozilla.org/integration/autoland/rev/35db4533f11f
Enable PerformanceEventTiming tests in Nightly r=smaug
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/27553 for changes under testing/web-platform/tests
Upstream PR merged by moz-wptsync-bot
Regressions: 1692213
Regressions: 1693327
Blocks: 1701029
You need to log in before you can comment on or make changes to this bug.