Automatic update from web-platform-testsUse NotFoundError instead of InvalidPointerId
This cl follows the new pointerevent spec which
uses more common WebIDL specified exception
NotFoundError instead of defining new
InvalidPointerId exception.
Bug: 885321
Change-Id: I28e946ffcb96c9fb4f70c76a4b9c09be620f981d
Reviewed-on: https://chromium-review.googlesource.com/1231990
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Ella Ge <eirage@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592903}
--
wpt-commits: c73ea25fec2bcede3bb0f622c4b9fc5076e7ff62
wpt-pr: 13059
Automatic update from web-platform-testsMerge pull request #13131 from Loirooriol/css-computed-insets-fix
Fix syntax and typos in tests from #12956
--
wpt-commits: 6718d7d67d65a2d3073bd29783f4ec6b76d47be8
wpt-pr: 13131
Automatic update from web-platform-testsUpdate doc regarding exp. features on Chrome
Following https://github.com/web-platform-tests/wpt/pull/13011, `wpt`
automatically turns on experimental web platform features on Chrome if
the channel is "dev". Update the doc to reflect this change.
--
wpt-commits: b0ea10809d150e8492bb20df51583e16a2f4f1ac
wpt-pr: 13129
Automatic update from web-platform-tests[service-workers] Refactor tautological tests (#13043)
* [service-workers] Refactor tautological tests
Previously, these tests created Promise values which would be fulfilled
even when expectations were violated. This would cause the test harness
to interpret them as "passing" regardless of implementation status.
Remove the use of `Promise.prototype.catch` to ensure that promise
rejections which occur during test execution lead to test failure.
--
wpt-commits: 3411e4bff0a7c875811e65398472cc6403619476
wpt-pr: 13043
Automatic update from web-platform-tests[docs] Remove obviated instructions
As of [1], the WPT CLI automatically inserts the
`--use-fake-ui-for-media-stream` and
`--use-fake-device-for-media-stream` arguments for the Chrome browser.
[1] a4eaa46ffebe5785562b930316a300423f23707e
--
wpt-commits: 70ca025c50fb6dc3b2f828de062e412d7897daf8
wpt-pr: 13126
Automatic update from web-platform-tests[Background Fetch] Set bad-status as failureReason
when one of the settled fetches has a response with a bad status.
Bug: 876691
Change-Id: I45af6b792a6a43e5b091bc5fe6f40d011bdabac5
Reviewed-on: https://chromium-review.googlesource.com/1233693
Reviewed-by: Rayan Kanso <rayankans@chromium.org>
Reviewed-by: Peter Beverloo <peter@chromium.org>
Commit-Queue: Mugdha Lakhani <nator@chromium.org>
Cr-Commit-Position: refs/heads/master@{#592836}
--
wpt-commits: 9dd846c1243e6a5631a8ddfc1b885cc14561ae0a
wpt-pr: 13079
Automatic update from web-platform-testsCheck completeness of images with and without srcset.
--
Remove trailing whitespace.
--
wpt-commits: 3216cb4d8d4ed83e1f0141fbad72000e04ff7494, 359e0bc27a1b3f3f834e21613d4b6b3a9d2fc168
wpt-pr: 13122
Automatic update from web-platform-testsRun all unit tests for resources/.
Because of a caching mechanism in pytest based on the fspath attribute of the
HTMLItem instances, only one test has run for the past few months.
This caused a change in the output of worker-dedicated.sub.html to go
unnoticed; I have changed the expected output to match.
Also, one of the subtests in exceptional-cases.html causes a timeout. The test
has never run in CI, so I removed the offending part.
--
Install the driver cleanup handler ASAP in resources/test/conftest.py.
This ensures the web browser is closed if the server fails to start.
--
wpt-commits: b869496ee3dbb2ab075c730fa2b029baa95cdcba, 126a0c4027177894934ed40d697145ee9fc28f51
wpt-pr: 13119
Automatic update from web-platform-testsCSSOM View Scroll Behavior tests: Catch exceptions in observeScrolling() so that the promise of the test is properly rejected. (#13104)
--
wpt-commits: efa946920503254905945bc4bb897380dce48f33
wpt-pr: 13104
- Various telemetry methods now need an object to be passed in in order to keep them seperate e.g. if the inspector is opened in tab 1 a timer is started. If an inspector is opened in tab 2 the same timer is restarted. Closing tab 2 would then erase the timing event invalidating the timer in tab 1.
- We no longer need to preface telemetry calls with category "devtools.main" because this is the only category we will be using.
- There are some changes to `devtools/client/debugger/new/dist/vendors.js` and `devtools/client/debugger/new/src/utils/telemetry.js` that need to be ported to the debugger at the same time as landing this.
Differential Revision: https://phabricator.services.mozilla.com/D6137
--HG--
extra : moz-landing-system : lando
With the Serde refactoring we have made this flag mandatory. This patch
reverts that change, and allows it to be skipped.
Differential Revision: https://phabricator.services.mozilla.com/D7050
--HG--
extra : moz-landing-system : lando
TabTarget.attach is being called from the toolbox, before opening the tools,
so we do not have to call it from panel's open functions, nor code that is opening
a toolbox right after.
MozReview-Commit-ID: 77TZFbvOaFt
Differential Revision: https://phabricator.services.mozilla.com/D6668
--HG--
extra : moz-landing-system : lando
This patch will remove setContest(), and change the following things instead of this:
* Use HTMLTooltip.panel.appendChild() instead of HTMLTooltip.setContent().
* Add HTMLTooltip.setContetnSize() to specify the panel size if need this.
Differential Revision: https://phabricator.services.mozilla.com/D7044
--HG--
extra : moz-landing-system : lando
SwatchBaseEditorTooltip specify the "topcentor bototmleft" to second parameter
of HTMLTooltip.show(). However, this parameter will ignore since show() function
require the second parameter as the object, not the string.
Bug 1307481 comment 42 has pointed out this parameter.
Differential Revision: https://phabricator.services.mozilla.com/D7043
--HG--
extra : moz-landing-system : lando
nsCSSFrameConstructor::FindDisplayData() guarantees a block with "display:
list-item" will be constructed by ConstructBlock() (either through
ConstructScrollableBlock() or ConstructNonScrollableBlock()).
This is also a preparation to fix bug 1491915 since we want to control
bullet frame creation under column hierarchy.
Depends on D6840
Differential Revision: https://phabricator.services.mozilla.com/D6841
--HG--
extra : moz-landing-system : lando
It's queried during layer building, for the RCD-RSF only. If we set it for
a subframe RSF, that overwrites the value for the RCD-RSF, and we end up
querying the incorrect value.
Differential Revision: https://phabricator.services.mozilla.com/D6536
--HG--
extra : moz-landing-system : lando
This adds the user prompt tests for those commands which clearly
have to handle the prompt. But it still leaves out those commands
where the behavior hasn't been clarified yet.
Differential Revision: https://phabricator.services.mozilla.com/D6927
--HG--
rename : testing/web-platform/tests/webdriver/tests/page_source/__init__.py => testing/web-platform/tests/webdriver/tests/get_page_source/__init__.py
rename : testing/web-platform/tests/webdriver/tests/page_source/source.py => testing/web-platform/tests/webdriver/tests/get_page_source/source.py
extra : moz-landing-system : lando
This patch isn't expected to change behavior; it's just some simplification.
Depends on D6976
Differential Revision: https://phabricator.services.mozilla.com/D6978
--HG--
extra : moz-landing-system : lando
This patch isn't expected to change behavior; it's just some simplification.
Differential Revision: https://phabricator.services.mozilla.com/D6976
--HG--
extra : moz-landing-system : lando
