[UserTimingL3] Make PerformanceTiming own its attribute name mapping
In the User Timing spec, it is an error to make a PerformanceMark with the same name as a read-only attribute from the PerformanceTiming interface[1]. E.g. it is an error to call `performance.mark("navigationStart")` as this would lead to ambiguity when trying to resolve calls like `performance.measure("m", "navigationStart")`. Since the read-only attributes are defined on the PerformanceTiming interface[2], it makes more sense to declare a name/attribute mapping locally instead of in the PerformanceUserTiming class. [1]: https://w3c.github.io/user-timing/#the-performancemark-constructor [2]: https://www.w3.org/TR/navigation-timing/#sec-navigation-timing-interface Bug: 805566 Change-Id: I2466d123a0d93965555c06d2434cb839fafabb72 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1967567 Commit-Queue: Tom McKee <tommckee@chromium.org> Reviewed-by:Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#733395}
Showing
Please register or sign in to comment