commit | 6be8927b9a3cd796e5389860797371ecdd5ae033 | [log] [tgz] |
---|---|---|
author | Nate Chapin <japhet@chromium.org> | Mon Jan 30 20:32:21 2023 |
committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Mon Jan 30 21:55:52 2023 |
tree | 6930e500c91627eb3fb37702231e31b561efaa83 | |
parent | c930eeba545c08b7896cbf8a93727f3c7c78a213 [diff] |
Move renderer-side same-url-replacement enforcement to LocalFrame::NavigationShouldReplaceCurrentHistoryEntry When we navigate to the current url, we treat it as a replacing navigation, rather than pushing a new history entry. The browser process enforces this most of the time, but there's a special case to enforce it in the renderer for synchronous same-document commits. This renderer process special case is in a weird place late in the commit process. The late timing is also a problem because the navigation API wants to report whether the navigation will replace the current history entry when it fires the navigate event. The navigate event fires before we enforce this policy currently. By moving same-url replacement to LocalFrame::NavigationShouldReplaceCurrentHistoryEntry, we duplicate some logic between the renderer and the browser process, but we consistently switch the navigation to be replacing before the navigate event fires, ensure we expose the correct navigation type to JS. Change-Id: I8859ac19fddbfc2f9aa42cad8e19b537df9679b1 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4189640 Commit-Queue: Nate Chapin <japhet@chromium.org> Reviewed-by: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/main@{#1098808}
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!