[UserTimingL3] {}, null, undefined passed to start treated as 0
According to the spec (https://w3c.github.io/user-timing/#measure-method), UserTimingL3 API has the second argument being: optional (DOMString or PerformanceMeasureOptions) startOrMeasureOptions This indicates that the arg cannot distinguish between: 1. null 2. {} 3. undefined 4. { invalidDictProperty } According to the spec: 3.1.3 measure() method... 3. Compute start time as follows.. 4. Otherwise, let start time be 0. When these indistinguishable values are passed, they should be interpreted as start time being 0. Bug: 953840 Change-Id: I052a7823d9ae8b27056f53f04a26fcc93421db75 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1691862 Commit-Queue: Liquan (Max) Gu <maxlg@chromium.org> Reviewed-by:Nicolás Peña Moreno <npm@chromium.org> Cr-Commit-Position: refs/heads/master@{#675873}
Showing
Please register or sign in to comment