Open Bug 1542173 Opened 5 years ago Updated 2 years ago

Anomalies in navigation timing API

Categories

(Core :: DOM: Core & HTML, defect, P3)

defect

Tracking

()

UNCONFIRMED

People

(Reporter: generalijoan, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

We couldn't reproduce it

Actual results:

From Generali Spain we are working on a new system to get the performance from our commercial agent network. The new performance metric are based on navigation timing API https://www.w3.org/TR/navigation-timing.

Expected results:

We collect around 119K hits/day from Firefox. We found around 490 (0.4%) anomalies distributed in:

Regards,
Joan

Not sure what to ask for here..moving over to a component, if it is not the proper one please assign it to the right one.

Component: Untriaged → DOM: Core & HTML
Product: Firefox → Core

baku, does this look actionable?

Flags: needinfo?(amarchesini)

Moving the NI to valentin.

Flags: needinfo?(amarchesini) → needinfo?(valentin.gosu)
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.