Summary: | [ Mac ] fast/dom/webtiming-document-open.html is a flaky failure | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Eric Hutchison <ehutchison> | ||||
Component: | DOM | Assignee: | Alex Christensen <achristensen> | ||||
Status: | RESOLVED FIXED | ||||||
Severity: | Normal | CC: | achristensen, ap, cdumez, ehutchison, mark.lam, webkit-bot-watchers-bugzilla, webkit-bug-importer | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
Eric Hutchison
2021-07-28 16:03:08 PDT
Updated test expectations at https://trac.webkit.org/changeset/280408/webkit. Created attachment 434532 [details]
Patch
Comment on attachment 434532 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=434532&action=review > Source/WebCore/page/PerformanceTiming.cpp:58 > return 0; Is it intentional in all these getters that we're not caching in early return cases? > Source/WebCore/page/PerformanceTiming.cpp:80 > + m_unloadEventStart = monotonicTimeToIntegerMilliseconds(timing->unloadEventStart()); nit: extra space Comment on attachment 434532 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=434532&action=review >> Source/WebCore/page/PerformanceTiming.cpp:58 >> return 0; > > Is it intentional in all these getters that we're not caching in early return cases? All those early returns are unlikely to be hit, and if we do and the website queries multiple times then we'll early return multiple times. This whole API has been replaced, MDN says it's deprecated and not to use it. It will be removed a bit after bug 227336 is fixed. |