commit | 49287d0e660dd6704c508ef20c9d53c13aee296b | [log] [tgz] |
---|---|---|
author | Dan H <harringtond@chromium.org> | Tue Feb 28 23:02:08 2023 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Tue Feb 28 23:15:05 2023 |
tree | a80ed5719dec1c412f2972dc433f4bcf8d6334cf | |
parent | 53a3c3f1d8fcaea434595d00ec4431038de1d49e [diff] |
Revert "Consolidate iframe & object resource timing code paths" This reverts commit 5dcb6f7b01d5f51144a9ba847c34bb0cdc344ccb. Reason for revert: MSan failures crbug.com/1420057 Original change's description: > Consolidate iframe & object resource timing code paths > > So far some of the logic in resource timing for subframe navigations > iframe/object/embed) was duplicated, e.g. both in blink and in content. > > This has led to race conditions, inconsistencies and sometimes > XSS leaks. > > This patch attempts to improve the situation by consolidating the code > paths: > > - NavigationRequest receives is_container_initiated, which ensures only > container-initiated navigations are reported to the parent. This > is a clarification of something that was ambiguous in the spec > previously (https://github.com/whatwg/html/issues/8846). > It later uses ParentResourceTimingAccess to decide if a navigation > should report to its parent with/without response details > (status code and mime-type), or not report at all (TAO-fail, not > an iframe, not container-initiated). > > - Both object fallbacks and cancelled navigations (204/205) report > to the parent via RenderFrameImpl, and blink converts that to a > ResourceTimingInfo object. This allows us to remove the duplicated > resource timing creation code in //content. > > - We report fallback resource timing also for plugin error events and > not only for load events. > > Bug: 1399862 > Bug: 1410705 > Change-Id: Id37d23cd02eee9e38f812e6f3da99caedafdee3d > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4214695 > Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org> > Reviewed-by: Daniel Cheng <dcheng@chromium.org> > Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org> > Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org> > Cr-Commit-Position: refs/heads/main@{#1110433} Bug: 1399862 Bug: 1410705 Bug: 1420057 Change-Id: Icfc5b6ca7ebd718b2fff58e3f5c7765c53ee93f9 No-Presubmit: true No-Tree-Checks: true No-Try: true Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4295881 Owners-Override: Dan H <harringtond@chromium.org> Reviewed-by: Dan H <harringtond@chromium.org> Commit-Queue: Dan H <harringtond@chromium.org> Bot-Commit: Rubber Stamper <rubber-stamper@appspot.gserviceaccount.com> Cr-Commit-Position: refs/heads/main@{#1110619}
The web-platform-tests Project is a cross-browser test suite for the Web-platform stack. Writing tests in a way that allows them to be run in all browsers gives browser projects confidence that they are shipping software that is compatible with other implementations, and that later implementations will be compatible with their implementations. This in turn gives Web authors/developers confidence that they can actually rely on the Web platform to deliver on the promise of working across browsers and devices without needing extra layers of abstraction to paper over the gaps left by specification editors and implementors.
The most important sources of information and activity are:
wpt:matrix.org
matrix channel; includes participants located around the world, but busiest during the European working day.If you'd like clarification about anything, don't hesitate to ask in the chat room or on the mailing list.
Clone or otherwise get https://github.com/web-platform-tests/wpt.
Note: because of the frequent creation and deletion of branches in this repo, it is recommended to “prune” stale branches when fetching updates, i.e. use git pull --prune
(or git fetch -p && git merge
).
See the documentation website and in particular the system setup for running tests locally.
The wpt
command provides a frontend to a variety of tools for working with and running web-platform-tests. Some of the most useful commands are:
wpt serve
- For starting the wpt http serverwpt run
- For running tests in a browserwpt lint
- For running the lint against all testswpt manifest
- For updating or generating a MANIFEST.json
test manifestwpt install
- For installing the latest release of a browser or webdriver server on the local machine.wpt serve-wave
- For starting the wpt http server and the WAVE test runner. For more details on how to use the WAVE test runner see the documentation.On Windows wpt
commands must be prefixed with python
or the path to the python binary (if python
is not in your %PATH%
).
python wpt [command]
Alternatively, you may also use Bash on Ubuntu on Windows in the Windows 10 Anniversary Update build, then access your windows partition from there to launch wpt
commands.
Please make sure git and your text editor do not automatically convert line endings, as it will cause lint errors. For git, please set git config core.autocrlf false
in your working tree.
The master branch is automatically synced to wpt.live and w3c-test.org.
Save the Web, Write Some Tests!
Absolutely everyone is welcome to contribute to test development. No test is too small or too simple, especially if it corresponds to something for which you've noted an interoperability bug in a browser.
The way to contribute is just as usual:
git checkout -b topic
../wpt lint
as described above.If you spot an issue with a test and are not comfortable providing a pull request per above to fix it, please file a new issue. Thank you!