-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WPT: Create function to test BFCache not restored reason #38038
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The review process for this patch is being conducted in the Chromium project.
4bede13
to
3767e01
Compare
Added a function `assertBFCacheNotRestoredReasonsIfApplicable` that uses the `notRestoredReasons` API. Unlike the helper functions in performance timing API folder, this one only checks the main frame's reasons, which should be good (and concise) enough for most of the BFCache feature WPTs. If the API is not available, the function will return straightaway instead report assertion failure. This CL also modifies back-forward-cache-open-connection.window.js as an example usage of the helper function. Bug: 1408436 Change-Id: Ia6215ae88bc295b9c2d8c164aab78780ded3606c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4177970 Reviewed-by: Fergal Daly <[email protected]> Reviewed-by: Yuzu Saijo <[email protected]> Commit-Queue: Mingyu Lei <[email protected]> Cr-Commit-Position: refs/heads/main@{#1098432}
3767e01
to
aa9c6b6
Compare
Some affected tests had slow results: Slow tests
These may be pre-existing or newly slow tests. Slow tests indicate that a test ran very close to the test timeout limit and so may become TIMEOUT-flaky in the future. Consider speeding up the test or breaking it into multiple tests. For help, please tag |
created crbug.com/1411564. @KyleJu @DanielRyanSmith can you pls admin merge? Thanks! |
Added a function `assertBFCacheNotRestoredReasonsIfApplicable` that uses the `notRestoredReasons` API. Unlike the helper functions in performance timing API folder, this one only checks the main frame's reasons, which should be good (and concise) enough for most of the BFCache feature WPTs. If the API is not available, the function will return straightaway instead report assertion failure. This CL also modifies back-forward-cache-open-connection.window.js as an example usage of the helper function. Bug: 1408436 Change-Id: Ia6215ae88bc295b9c2d8c164aab78780ded3606c Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4177970 Reviewed-by: Fergal Daly <[email protected]> Reviewed-by: Yuzu Saijo <[email protected]> Commit-Queue: Mingyu Lei <[email protected]> Cr-Commit-Position: refs/heads/main@{#1098432} Co-authored-by: Mingyu Lei <[email protected]>
Added a function
assertBFCacheNotRestoredReasonsIfApplicable
thatuses the
notRestoredReasons
API. Unlike the helper functions inperformance timing API folder, this one only checks the main frame's
reasons, which should be good (and concise) enough for most of the
BFCache feature WPTs.
If the API is not available, the function will return straightaway
instead report assertion failure.
This CL also modifies back-forward-cache-open-connection.window.js
as an example usage of the helper function.
Bug: 1408436
Change-Id: Ia6215ae88bc295b9c2d8c164aab78780ded3606c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4177970
Reviewed-by: Fergal Daly <[email protected]>
Reviewed-by: Yuzu Saijo <[email protected]>
Commit-Queue: Mingyu Lei <[email protected]>
Cr-Commit-Position: refs/heads/main@{#1098432}