Open Bug 1667836 Opened 4 months ago Updated 9 days ago

Prototype PerformanceEventTiming

Categories

(Core :: Performance, enhancement, P3)

enhancement

Tracking

()

People

(Reporter: sefeng, Assigned: sefeng)

References

(Depends on 1 open bug)

Details

Attachments

(6 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

You need to log in before you can comment on or make changes to this bug.