Closed Bug 1956809 Opened 7 months ago Closed 2 months ago

Enable PerformanceEventTiming.interactionId

Categories

(Core :: DOM: Performance APIs, task, P3)

task

Tracking

()

RESOLVED FIXED
144 Branch
Tracking Status
relnote-firefox --- 144+
firefox144 --- fixed

People

(Reporter: canova, Assigned: canova)

References

Details

(Keywords: dev-doc-complete)

Attachments

(1 file)

We implemented PerformanceEventTiming.interactionId behind a pref in bug 1934683. Currently there are some spec issues, which are also mentioned in that bug. We should enable the dom.performance.event_timing.enable_interactionid pref once the spec issues and wpt test issues are resolved.

We can also enable it in Nightly only first, so that we can get interop numbers

Yeah, that's a good idea. I can file a new bug for enabling it on Nightly. Do you think we should do it now/soon or after some spec PRs are created?

I think we can do it now, because Nightly isn't considered as shipped..so nobody should complaint about that :)

Sounds good, will do it in bug 1957012!

Assignee: nobody → canaltinova
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED
Target Milestone: --- → 144 Branch

:canova, we can add a release note for this now that it's enabled (Process info)

The following wording was used when this was nightly only. Any changes, or do you want to use the same wording?

Firefox now supports PerformanceEventTiming.interactionId, allowing developers to group related input events. This enables support for the Interaction to Next Paint (INP) responsiveness metric.

Flags: needinfo?(canaltinova)

Yes, it would be great to add a release note for it. The same wording looks good to me.

(pasting my previous relnotes request for posterity)

Release Note Request (optional, but appreciated)
[Why is this notable]:
This adds support for the interactionId attribute in the PerformanceEventTiming API, which is used to calculate the "Interaction to Next Paint" (INP) metric—part of Core Web Vitals. It helps analyze responsiveness and debug long task delays by grouping related input events.
[Affects Firefox for Android]: Yes
[Suggested wording]:
Added support for PerformanceEventTiming.interactionId, allowing developers to group related input events. This enables support for the Interaction to Next Paint (INP) responsiveness metric.
[Links (documentation, blog post, etc)]:
https://developer.mozilla.org/en-US/docs/Web/API/PerformanceEventTiming/interactionId
https://developer.mozilla.org/en-US/docs/Glossary/Interaction_to_next_paint
https://web.dev/articles/inp

relnote-firefox: --- → ?
Flags: needinfo?(canaltinova)

Thanks, added to the Fx144 nightly release notes, please allow 30 minutes for the site to update.
Keeping the relnote-firefox flag as ? to keep it on the radar for inclusion in the final Fx144 release notes.

Summary: Enable PerformanceEventTiming.interactionId once the spec issues are resolved → Enable PerformanceEventTiming.interactionId
QA Whiteboard: [qa-triage-done-c145/b144]

Added to the Fx144 release notes

The related browser compat data also needs to be updated. Therefore I've added the dev-doc-needed flag.

Sebastian

Keywords: dev-doc-needed

FF144 MDN work for this can be tracked in https://github.com/mdn/content/issues/41409. Very minor - compat data work had already been picked up and this had docs. Just and MDN release note and removal from experimental features page.

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

Attachment

General

Created:
Updated:
Size: