commit | 3b225ddbdfdc100a4095ab3fd83a5b33d2e16fac | [log] [tgz] |
---|---|---|
author | Masayuki Nakano <masayuki@d-toybox.com> | Thu Dec 01 05:24:51 2022 |
committer | moz-wptsync-bot <wptsync@mozilla.com> | Fri Dec 02 09:25:56 2022 |
tree | 072a4786618bcea8048044963ca85e0d169a6333 | |
parent | e1400ef4581676b52364c3c7b9587c705c564ab9 [diff] |
part 1: Make `bold`, `italic` and `strikethrough` tests treat `<strong>`, `<em>` and `<s>` as what browsers do I think that the tests were based on Gecko's behavior (and `strikethrough.js` expects `<s>` as default container of `execCommand("strikethrough")` but all browsers use `<strike>`, I guess that the original test author was confused). Blink and WebKit don't use near these elements as existing container of alternatives of `<b>`, `<i>` and `<strike>`. I think that this makes sense because for example `<b>` represents bold style but `<strong>` represents emphasize the text. This patch makes the tests align to Blink/WebKit and most new expectations are copied from Blink's result. Exception is, Blink/WebKit replaces rightmost `<s>` when middle of it is unstyled only in some cases with `<strike>` or `<span>`. This must be a leak of their implementation, and hard to follow it because the simplest approach of partially removing style is, split the existing element at 2 points and unwrap middle element children. I.e., it's not required to touch the rightmost element. Differential Revision: https://phabricator.services.mozilla.com/D163185 bugzilla-url: https://bugzilla.mozilla.org/show_bug.cgi?id=1802668 gecko-commit: 669016166d0cb7d0edbbbbe0ae81726974e12b3f gecko-reviewers: m_kato
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!