| commit | d83084ba138d59b0b41bc87067bdf0f79e350c24 | [log] [tgz] |
|---|---|---|
| author | Henrik Boström <hbos@chromium.org> | Wed Oct 18 12:55:34 2023 |
| committer | Blink WPT Bot <blink-w3c-test-autoroller@chromium.org> | Wed Oct 18 13:17:08 2023 |
| tree | f1635746e5cce5d8c34c51a54dd9eefe08dbf974 | |
| parent | 42cf389f733d8921972d3a7dc2662535fda563a9 [diff] |
[Track Stats] Remove support for non-gUM/gDM tracks. In a defensive stance (in terms of implementer burdon), the track.stats API was only defined for getUserMedia/getDisplayMedia-based sources. - This is a shame, because video processing is gaining popularity and it would be great to be able to know about frame counters for these non-device tracks as well. Based on implementation experience, this does seem unnecessary and I filed https://github.com/w3c/mediacapture-extensions/issues/102, but for now this API should only be applicable to "device"-backed tracks. It's possible there could be more implementation burdon if it turns out that other sources are able to drop frames early (meaning, before the VideoTrackAdapter sees the frame), because if so we need to wire up the OnFrameDropped callback to all source implementations. But for now my understanding is that "early" OnFrameDropped is only applicable on real-time devices and that supporting all types of tracks would have been no extra effort. But until we can confirm this and convince the WG, let's align with the spec and throw an exception on non-device sources. # Skipping unrelated slow bot NOTRY=True Bug: chromium:1472978 Change-Id: I5cc40c07303a9e87d76105fb3dbf03b7259dd72f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4946414 Commit-Queue: Henrik Boström <hbos@chromium.org> Commit-Queue: Harald Alvestrand <hta@chromium.org> Reviewed-by: Harald Alvestrand <hta@chromium.org> Cr-Commit-Position: refs/heads/main@{#1211445}
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!