mirror of
https://github.com/HeyPuter/firefox.git
synced 2026-11-15 17:55:15 -10:00
4e94de9f6dc14a3068e626b70ff20e652fedad51
8
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
5e4e916e12 |
Bug 1848177 [wpt PR 41410] - sensors: Convert existing Generic Sensor web tests to test_driver, a=testonly
Automatic update from web-platform-tests
sensors: Convert existing Generic Sensor web tests to test_driver (#41410)
All Generic Sensor web tests are now using virtual sensors and their
implementation in WPT's testdriver.js and ChromeDriver/content_shell.
These tests no longer depend on generic_sensor_mocks.js (or Mojo mocks
in general), which has been kept only for the Device Orientation tests
at this point, and should be fully interoperable now. This also
exercises the code in //content and //services.
Compared to the JS mocks-based implementation, one of the biggest
changes is that there is no equivalent to a MockSensor that takes an
array of readings and periodically rotates and reports them to
consumers. This was an implementation detail that was kind of hard to
justify in spec terms, and the interaction between the JS timer and the
C++ code in services could lead to races between shared buffer values
and expected values (bug
|
||
|
|
39a46a36ba |
Backed out 197 changesets (bug 1861850, bug 1862453, bug 1862476, bug 1856528, bug 1860877, bug 1843733, bug 1861537, bug 1860936, bug 1862598, bug 1861247, bug 1862961, bug 1862371, bug 1860728, bug 1861515, bug 1861619, bug 1862286, bug 1862036, bug 1859849, bug 1861335, bug 1862047, bug 1862771, bug 1861272, bug 1863416, bug 1862114, bug 1862610, bug 1859209, bug 1862582, bug 1861393, bug 1861968, bug 1861379, bug 1860795, bug 1861382, bug 1862523, bug 1863339, bug 1862948, bug 1858096, bug 1862365, bug 1862770, bug 1861422, bug 1863305, bug 1861469, bug 1861276, bug 1862613, bug 1860852, bug 1860876, bug 1862673, bug 1861601, bug 1862524, bug 1862784, bug 1860537, bug 1862441, bug 1852577, bug 1863338, bug 1862725, bug 1857638, bug 1862976, bug 1862313, bug 1850389, bug 1861607, bug 1863151, bug 1861514, bug 1861654, bug 1860545, bug 1862078, bug 1861465, bug 1862044, bug 1862342, bug 1860498, bug 1862041, bug 1862479, bug 1860929, bug 1863261, bug 1862098, bug 1862108, bug 1861525, bug 1863275, bug 1862042, bug 1861832, bug 1862032, bug 1861240, bug 1861934, bug 1862520, bug 1863341, bug 1861368, bug 1861470, bug 1863422, bug 1862248, bug 1862699, bug 1862636, bug 1863087, bug 1861851, bug 1863685, bug 1860132, bug 1857517, bug 1862477, bug 1848177, bug 1862209, bug 1844187, bug 1859075, bug 1862733, bug 1862259, bug 1862341, bug 1862006, bug 1861964, bug 1861541, bug 1858876, bug 1862324, bug 1862201, bug 1861532, bug 1861284, bug 1862110, bug 1862642, bug 1861440, bug 1848515, bug 1862612, bug 1848182, bug 1861523, bug 1863297, bug 1863448, bug 1860178, bug 1861274, bug 1861511, bug 1860917, bug 1859008, bug 1862793, bug 1861829, bug 1863376, bug 1861518, bug 1862820, bug 1860871, bug 1861278, bug 1861244, bug 1861966, bug 1860846, bug 1862329, bug 1859658) because the patched did not work for talos failures like "No module named 'h2'" CLOSED TREE
Backed out changeset f24907dcdbbe (bug 1863685) Backed out changeset eeb471640cdd (bug 1863685) Backed out changeset 84d559a627aa (bug 1863685) Backed out changeset 8a2ef96f9c62 (bug 1863685) Backed out changeset fb194e8aa4c3 (bug 1863685) Backed out changeset f4422bef270e (bug 1863275) Backed out changeset 86e7318928c5 (bug 1863275) Backed out changeset 3f39b0edfc4d (bug |
||
|
|
8985a05b55 |
Bug 1848177 [wpt PR 41410] - sensors: Convert existing Generic Sensor web tests to test_driver, a=testonly
Automatic update from web-platform-tests
sensors: Convert existing Generic Sensor web tests to test_driver (#41410)
All Generic Sensor web tests are now using virtual sensors and their
implementation in WPT's testdriver.js and ChromeDriver/content_shell.
These tests no longer depend on generic_sensor_mocks.js (or Mojo mocks
in general), which has been kept only for the Device Orientation tests
at this point, and should be fully interoperable now. This also
exercises the code in //content and //services.
Compared to the JS mocks-based implementation, one of the biggest
changes is that there is no equivalent to a MockSensor that takes an
array of readings and periodically rotates and reports them to
consumers. This was an implementation detail that was kind of hard to
justify in spec terms, and the interaction between the JS timer and the
C++ code in services could lead to races between shared buffer values
and expected values (bug
|
||
|
|
d691ed6c8a |
Bug 1579320 [wpt PR 18886] - [sensor] Upstream sensor layout tests to wpt, a=testonly
Automatic update from web-platform-tests [sensor] Upstream sensor layout tests to wpt Rewrote /external/wpt/resources/chromium/generic_sensor_mocks.js to align with /http/tests/resources/sensor-helpers.js, but excluded those functions specific for device orientation. Merged tests from /sensor/resources/generic-sensor-tests.js to /external/wpt/generic-sensor/generic-sensor-tests.js Moved common utils into /external/wpt/generic-sensor/resources/generic-sensor-helpers.js Merged tests from /sensor/*.html to corresponding test folders under /external/wpt/, e.g. sensor/orientation-sensor.html -> external/wpt/orientation-sensor/OrientationSensor.https.html Updated all sensor tests under external/wpt/ to adapt to sensor mojom mocks Deleted folder web_tests/sensor/ Bug: 816462 Change-Id: I614ce82b7c90530b7a268d8f6a0f72cc96ea3d6f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1770158 Commit-Queue: Wanming Lin <[email protected]> Reviewed-by: Reilly Grant <[email protected]> Cr-Commit-Position: refs/heads/master@{#695905} -- wpt-commits: db7bad01d261a21cb99405abb57f9dd7a421e147 wpt-pr: 18886 |
||
|
|
40d51ff3fb |
Bug 1532639 [wpt PR 15630] - Add <meta name=timeout content=long> to WPT in SlowTests, a=testonly
Automatic update from web-platform-tests Add <meta name=timeout content=long> to WPT in SlowTests This is the 2nd step in the process of banning external/wpt from SlowTests. After cleaning up the wtp entries we're marking them as slow by using wpt idioms, i.e.: 1) Add <meta name="timeout" content="long"> to .html files 2) Add // META: timeout=long to .js files Bug: 765026 Change-Id: Iaf051104f419524916e19324996cc36ee37d5426 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497005 Commit-Queue: Sergio Villar <[email protected]> Reviewed-by: Andy Paicu <[email protected]> Reviewed-by: Robert Ma <[email protected]> Cr-Commit-Position: refs/heads/master@{#643402} -- wpt-commits: 7287608f90f6b9530635d10086fd2ab386faab38 wpt-pr: 15630 |
||
|
|
e3a19c4cdc |
Backed out 222 changesets (bug 1544415 et al.) for webauthn failures/passes on Windows 7 debug and service-workers/service-worker/waiting.https.html failure on Linux x64 debug. a=backout CLOSED TREE
Backed out changeset fc657d55eb97 (bug 1544415) Backed out changeset 9087215a7000 (bug 1540826) Backed out changeset 9590c42d7255 (bug 1541659) Backed out changeset 20eeca8c7d6b (bug 1535863) Backed out changeset e5805636092b (bug 1541657) Backed out changeset 70bd8b8faa3a (bug 1541651) Backed out changeset 8708c42aa969 (bug 1528145) Backed out changeset 93fffda72fbb (bug 1541642) Backed out changeset 4d4ac12ce4f5 (bug 1541637) Backed out changeset 94a7fba447cf (bug 1541236) Backed out changeset 72e1adbc9b4a (bug 1537693) Backed out changeset 3aa4a44c3bdb (bug 1537730) Backed out changeset 7e0d6b7e646b (bug 1541338) Backed out changeset 22d170dba90e (bug 1539829) Backed out changeset 70137a989042 (bug 1541630) Backed out changeset ebc3e24f1d33 (bug 1535520) Backed out changeset 21efc1b6a079 (bug 1541098) Backed out changeset 9fb4d78b7ec3 (bug 1532672) Backed out changeset 67b8f25a8733 (bug 1540567) Backed out changeset ec5281021c22 (bug 1541621) Backed out changeset 6ebe1b1ebeac (bug 1540979) Backed out changeset 54dede13dc12 (bug 1540979) Backed out changeset 07216b84c388 (bug 1540022) Backed out changeset f0294cf3eb42 (bug 1539650) Backed out changeset 23a225d2d306 (bug 1540738) Backed out changeset 47d97703ac74 (bug 1540284) Backed out changeset 1814feb1d3d9 (bug 1540028) Backed out changeset 430ffa52a25b (bug 1540007) Backed out changeset 864a8f5738f7 (bug 1539996) Backed out changeset 1c329cd3b21f (bug 1540363) Backed out changeset 91adce7e0f23 (bug 1534865) Backed out changeset 215c1202d414 (bug 1534865) Backed out changeset 3e6e29d51857 (bug 1540045) Backed out changeset 3191e6048eeb (bug 1540431) Backed out changeset d4926fbb9647 (bug 1540405) Backed out changeset 8e6a1a9e8b99 (bug 1539880) Backed out changeset 1972694bafbe (bug 1540400) Backed out changeset e76da31c2ad1 (bug 1540393) Backed out changeset 614122ed4f55 (bug 1540393) Backed out changeset ba8d6e98b620 (bug 1540306) Backed out changeset 862697ae8fc6 (bug 1535908) Backed out changeset f1936f1dbd97 (bug 1539669) Backed out changeset 97941a89d110 (bug 1540252) Backed out changeset ce8a3d032f57 (bug 1540050) Backed out changeset 35a4149bcc9c (bug 1540184) Backed out changeset 632ad07f036c (bug |
||
|
|
6fd2c1c580 |
Bug 1532639 [wpt PR 15630] - Add <meta name=timeout content=long> to WPT in SlowTests, a=testonly
Automatic update from web-platform-tests Add <meta name=timeout content=long> to WPT in SlowTests This is the 2nd step in the process of banning external/wpt from SlowTests. After cleaning up the wtp entries we're marking them as slow by using wpt idioms, i.e.: 1) Add <meta name="timeout" content="long"> to .html files 2) Add // META: timeout=long to .js files Bug: 765026 Change-Id: Iaf051104f419524916e19324996cc36ee37d5426 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1497005 Commit-Queue: Sergio Villar <[email protected]> Reviewed-by: Andy Paicu <[email protected]> Reviewed-by: Robert Ma <[email protected]> Cr-Commit-Position: refs/heads/master@{#643402} -- wpt-commits: 7287608f90f6b9530635d10086fd2ab386faab38 wpt-pr: 15630 |
||
|
|
a193ebefeb |
Bug 1467820 [wpt PR 11426] - [sensors] Check that sensor frame and focused frame of same origin, a=testonly
Automatic update from web-platform-tests[sensors] Check that sensor frame and focused frame of same origin In order to implement mitigation stragegy defined in [1], focused frame and frame associated with the sensor should be of the same origin. [1] https://www.w3.org/TR/generic-sensor/#focused-area Bug: 849501 Change-Id: I06fce4e66873cd98e59e45d00ffe27de8e7d66f9 Reviewed-on: https://chromium-review.googlesource.com/1087049 Reviewed-by: Daniel Cheng <[email protected]> Reviewed-by: Reilly Grant <[email protected]> Commit-Queue: Alexander Shalamov <[email protected]> Cr-Commit-Position: refs/heads/master@{#566096} -- wpt-commits: 46fe6803fdd163e21137ba06b81558d6ba34ad12 wpt-pr: 11426 |