The refactoring of the webdriver crate to use Serde (bug 1396821)
caused this regression. By instructing Serde to correctly rename
both properties fixes it.
Differential Revision: https://phabricator.services.mozilla.com/D7079
--HG--
extra : moz-landing-system : lando
Split nsHostRecord into AddrHostRecord and TypeHostRecord for standard address dns queries and queries by-type.
Differential Revision: https://phabricator.services.mozilla.com/D6130
--HG--
extra : moz-landing-system : lando
Persistent notifications were not properly distinguished from clearable notifications
because they would first start as not persistent and got updated afterwards. Also added
a handle action in BrowserApp's onCreate for whenever the process gets removed.
Differential Revision: https://phabricator.services.mozilla.com/D6815
--HG--
extra : moz-landing-system : lando
We're trying to insert a table caption via an append into a display: contents
element. We pass the content-insertion-frame (the table frame) instead of the
siblings' parent (the table wrapper frame).
This is the right thing to pass though, we adjust the caption parent frame
later, on AdjustCaptionParentFrame, and we ensure that we don't get here for a
non-caption thing because of IsValidSibling (though note that that can actually
lie, see bug 1424656, we'd get the layout wrong if the title element was a
replaced element for example), so a normal append without a previous sibling
will still be correct.
It'd be nice to make this a bit less messy, fwiw, but I don't have the ideas or
the time to do it now.
Differential Revision: https://phabricator.services.mozilla.com/D7067
--HG--
extra : moz-landing-system : lando
Summary:
create LazyActorClass based off ObservedActorFactory and RegisterdFactory classes for use in RootActor and BrowsingContextActor;
Depends on D6468
Reviewers: ochameau
Reviewed By: ochameau
Bug #: 1473513
Differential Revision: https://phabricator.services.mozilla.com/D6470
--HG--
rename : devtools/server/actors/common.js => devtools/shared/protocol/lazy-pool.js
extra : rebase_source : 09a1c8eac3cbb5856a5e3e61a1c0540efe32e5bd
Automatic update from web-platform-testsUpdate marionette_driver from 2.6.0 to 2.7.0 (#10805)
--
wpt-commits: 23c54943daee3cd8520a6d86acc055f1120f96ad
wpt-pr: 10805
Automatic update from web-platform-testsVarious test fixes for python3 support. (#11769)
--
wpt-commits: 5bd512cdc76f762662915a2d3d9e49b021f14ff6
wpt-pr: 11769
Automatic update from web-platform-testsRemove WebKitAnimationEvent
This is an obsolete prefixed alias of AnimationEvent. An
intent-to-remove has been sent, and has got LGTM*3.
Blink intent thread: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/EgMUDqySZwE
Bug: 695504
Change-Id: Ia86e830fe3f653aa6a7b2f983afb75fd4d088831
Reviewed-on: https://chromium-review.googlesource.com/1238497
Commit-Queue: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Tim Volodine <timvolodine@chromium.org>
Reviewed-by: Rick Byers <rbyers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593405}
--
wpt-commits: 1c99c70996f35332b8a65040bf745f19678a6686
wpt-pr: 13149
Automatic update from web-platform-tests[testharness.js] Remove deprecated API (#12976)
[testharness.js] Remove deprecated API
The testharness.js functions `assert_exists` and `assert_not_exists`
have been labeled "deprecated" since 2012-01-31 [1]. Remove the
functions and replace all existing references with equivalent
assertions.
[1] 1780607fc4582b65b7fcdded3e39e79e95c8d915
--
wpt-commits: efa1c1e224cf7910008d37477beb954d41448ace
wpt-pr: 12976
Automatic update from web-platform-testsMake is_html actually work in Output#resolve_log().
In particular, is_html would never become true if SVGSVGElement was supported
at all.
Even if SVGSVGElement was not supported, it would never become true because
we were checking the namespace and localName of the Document object, rather
than the root element.
--
wpt-commits: 7f3e17fe6d5d48b0090b7b176fa5175037580654
wpt-pr: 13121
Automatic update from web-platform-testsUpdate selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.13.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
Update selenium from 3.14.0 to 3.14.1
--
wpt-commits: fab6e8e35344dc06267d1ba5a75780d0e0f3a6fc, ee8755b0f6cdaf901cf04c35a862070036e2df69, bc3d67c0658a7dd890c72c6bb896476014b65889, 3328d27dd5c1218c541baf9fd52cc981761867c8, 90d366cb68e06d42022f32065a568190b014a5fd, f5de401ce433e130cd2d1d015697bed544cf8654, 24c572a0727f8b2fe193b84024288b4b51bb3cef
wpt-pr: 13133
Automatic update from web-platform-testsCheck if platform is Windows before catching WindowsError
Check if the platform is Windows and the error is a WindowsError before
trying to run git.bat, as WindowsError is not defined in non-Windows.
Closes https://github.com/web-platform-tests/wpt/issues/12693
--
wpt-commits: 82d852bda1e08948858389c17402fa0571bc2584
wpt-pr: 13177
Automatic update from web-platform-testsAlso ignore ERROR in slow test check
Tweak the docstring accordingly to explain why.
--
wpt-commits: 130669061c6f4b475e1189ef107010966d686324
wpt-pr: 13158
Automatic update from web-platform-tests[wptrunner] Fix support for `--binary-arg` in Fx (#13154)
In order to automate Firefox, wptrunner requires the browser's internal
module "Marionette" to be enabled. This is a requirement regardless of
any custom configuration specified by the user, including additional
command-line flags via the `--binary-arg` argument.
Previously, this project would omit the `-marionette` argument in the
presence of any user-specified arguments. Because this interferes with
normal operation (and because the source code is formatted in a way that
conflicts with the order of operations), this is likely an unintentional
behavior.
Modify the code which derives the command-line arguments to always
include the `-marionette` argument.
--
wpt-commits: 3a749a13168916563b9611528b18d0376f04aab1
wpt-pr: 13154
Automatic update from web-platform-testsMerge pull request #13179 from yoavweiss/multiple_wildcard_test
[resource-timing] Add TAO test for multiple wildcards
--
wpt-commits: 3d117ae1266e6bd039a3a1ab92b27e82c3ccc92d
wpt-pr: 13179
Automatic update from web-platform-testsUnbreak html/dom/interfaces.https.html
This change makes /interfaces/touch-events.idl get fetched, rather
than /interfaces/touchevents.idl (which doesn't exist).
--
wpt-commits: 5d58e091e71aa3162fe9d0e40858351c8063ca08
wpt-pr: 13172
Automatic update from web-platform-tests[service-workers] Return value in cleanup (#13163)
Previously, many tests un-registered service workers using the
testharness.js API `add_cleanup` without returning the promise which
tracked the operation. While this ensured the operation was started at
the completion of the test, it did not guarantee that the operation
would be completed before the test was considered "complete."
In automation scenarios where many tests are executed in rapid
succession, this enabled a race condition: the navigation could
interrupt the un-registration process. In order to account for the
possibility of registrations that persisted from previous test failures,
the tests included "setup" code to defensively un-register such workers.
The `Test#add_cleanup` method was recently extended to support
asynchronous "clean up" operations [1]. Use that API to ensure tests are
not considered "complete" until after service worker un-registration is
done.
[1] https://github.com/web-platform-tests/wpt/pull/8748
--
wpt-commits: 7897f9d5beff624590d2fc254d2a7eca6e2b1e8f
wpt-pr: 13163
Automatic update from web-platform-testsMerge pull request #13159 from web-platform-tests/fix-mplus-1p-regular
Fix the path of mplus-1p-regular.woff in all tests
--
wpt-commits: eb68211270c6deb66eb928799a75e6af3b8db1b0
wpt-pr: 13159
Automatic update from web-platform-testsFix scrollIntoView(...) for SVG elements
AbsoluteBoundingBoxRectForScrollIntoView and associated helpers did not
compute the correct bounding box for SVG shapes (or anything but the SVG
root.)
Compute the bounding rect using the stroke bounding box.
Bug: 803440
Change-Id: If25ca98b686f17a0db699e569460cb4c276f06a0
Reviewed-on: https://chromium-review.googlesource.com/1238458
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#593306}
--
wpt-commits: b3ca0cee4b0772e615334e4155556ec254dab7b1
wpt-pr: 13145
Automatic update from web-platform-tests[css-layout-api] Move perform-child-layout tests to child-constraints
As above, move similar tests into subdirectory, and apply minor
documentation cleanups.
Adds two new tests checking that setting an invalid (negative) available
size, clamps it to zero.
Bug: 726125
Change-Id: Id5bdfa25970a4e4bfe359377b88176043ab1f6c3
Reviewed-on: https://chromium-review.googlesource.com/1236266
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593236}
--
wpt-commits: 80fa83f6ca3dc7039088afae9a908222b31f6aa4
wpt-pr: 13130
Automatic update from web-platform-tests[css-layout-api] Adds ability to specify percentage{Inline,Block}Size.
This allows developers to specify the size which percentages in the
block (wrt child writing mode) direction should be resolved against.
Currently inline percentages still resolve against the available
inline-size.
This adds a "OverrideContainingBlockPercentageResolutionLogicalHeight"
field on layout box, which both the logic for
LayoutBox::ComputePercenatgeLogicalHeight and
LayoutBox::ComputeReplacedLogicalHeight use.
They follow similar logic to LayoutGrid, in that in quirks mode,
percentages are treated as indefinite (doesn't "walk-up" the tree).
Change-Id: I256381687d2eed7693a908074f7f5032d5963e2b
Reviewed-on: https://chromium-review.googlesource.com/1232206
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593208}
--
wpt-commits: 159da2f8ef7c8259c7fc013cbfea2314e2dfdeeb
wpt-pr: 13124
Automatic update from web-platform-tests[css-properties-values-api] Use inherited value for substitution.
When a var()-reference produces tokens that are incompatible with the
current syntax, or the var()-reference refers to a variable that does not
exist, we currently always substitute the initial value, even for
inherited properties. This is incorrect, as the value should behave as
'unset', which means 'inherit' for inherited properties.
Note that if syntax-incompatible tokens are specified directly (not via a
var()-reference), we correctly behave as 'unset'. This is because the
var()-less case is handled by a different code path (variable.cc).
R=futhark@chromium.org
Bug: 641877
Change-Id: Ifdd5435ee77f4b8cd3998967713cb6fcb7e8d5f4
Reviewed-on: https://chromium-review.googlesource.com/1235579
Commit-Queue: Anders Ruud <andruud@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#593145}
--
wpt-commits: 689968f390a8c5c897ab5c9fa0f6fe27a40b5cc3
wpt-pr: 13120
