geckodriver should log to which host and port it is trying
to create a connection with Marionette.
MozReview-Commit-ID: DxWSsDDMKCL
--HG--
extra : rebase_source : df870bf956d93aae8d95f70c88c184adc90bf2bf
This patch fixes the addition of baseline tests into self.suites when the suite doesn't exist, and we are iterating over self.suites. Now, we find all baseline tests to run, then add them into self.suites when we are not iterating over self.suites.
MozReview-Commit-ID: GPQeCw1J9P3
--HG--
extra : rebase_source : c6fdfddea15a9e261431f03266784a932318b12f
Following the move to use cargo worktrees in central, the .gitignore
file for mozversion is not used anymore since we no longer generate
testing/mozbase/rust/mozversion/target on building.
MozReview-Commit-ID: 72geBjNxjZl
--HG--
extra : rebase_source : d7f11b33c91407e97416344ca1a2d0f06aa573d3
Mercurial, unlike git, does not pick up .hgignore files in subdirectories.
This file has never been used.
MozReview-Commit-ID: 6HdQJREJkgC
--HG--
extra : rebase_source : 9f69c19aa68b34e32efee6a400653210afe32018
Automatic update from web-platform-testsURL: host setter with default port against URL with non-default port
See https://github.com/nodejs/node/pull/20479.
--
wpt-commits: f0fe4791f5b87491d8d9662832fae543e4edbca1
wpt-pr: 10892
Automatic update from web-platform-testsReadableStreamBytesConsumer should check read results
ReadableStreamBytesConsumer expected that the results from
ReadableStreamReaderDefaultRead should be Promise<Object> because that
is provided from ReadableStream provided by blink, but it's possible to
inject arbitrary values with the promise assimilation.
This CL adds additional checks for such injection.
Bug: 840320
Change-Id: I7b3c6a8bfcf563dd860b133ff0295dd7a5d5fea5
Reviewed-on: https://chromium-review.googlesource.com/1049413
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556751}
--
wpt-commits: fc03b170c13c2377f852b35854682c573067d8d8
wpt-pr: 10886
Automatic update from web-platform-testsAdd support for JS shell tests to the manifest code.
--
wpt-commits: 8b105455a9b1fba8ca4cd7f973c565ca361278f5
wpt-pr: 10769
Automatic update from web-platform-testsHTML: FormData representation of <input type=file> without selection
For https://github.com/whatwg/html/pull/3658.
--
wpt-commits: 11f912ed1d8c8da3cb23f8e77444c4bc03c18e01
wpt-pr: 10865
Automatic update from web-platform-testsWorker: Throw an exception when importScripts() is called on "module" worker
Spec: https://html.spec.whatwg.org/multipage/workers.html#dom-workerglobalscope-importscripts
"1. If worker global scope's type is "module", throw a TypeError exception."
Bug: 831420
Change-Id: I6a1976363435596562689988ed39394a3b735779
Reviewed-on: https://chromium-review.googlesource.com/1038926
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556713}
--
wpt-commits: 42ae4a432d5264eba6c7171c8ecfcb26dc9fa1a8
wpt-pr: 10776
Automatic update from web-platform-testsDOM: non-Text nodes are not touched by normalization
This test makes sure that non-Text nodes are not touched even if they
hold empty text strings. This test was motivated by a bug present in
the jsdom library.
--
wpt-commits: d50825bfd2a2e887c24e63683a03efe5896e2b80
wpt-pr: 10735
Automatic update from web-platform-testswebrtc wpt: pass test in promise_test and async_test
passes the test argument in promise_test and async_test
so it can be used to add cleanup.
Change done with a jscodeshift codemod that detects
there were no arguments to promise_test (or async_test):
export default function transformer(file, api) {
const j = api.jscodeshift;
return j(file.source)
// .find(j.CallExpression)
.find(j.CallExpression, {callee: {type: 'Identifier', name: 'promise_test'}})
.forEach(path => {
if (path.value.arguments[0].params.length === 0) {
path.value.arguments[0].params.push(j.identifier('t'));
}
})
.toSource();
};
BUG=836871
Change-Id: Ie7dd7fb0dd8a4da6c4c00f3616fd41d1d47854ef
Reviewed-on: https://chromium-review.googlesource.com/1047674
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556711}
--
wpt-commits: 9949cb53d1e32bc9c34c687d8b89dc3ecb6d9553
wpt-pr: 10884
Automatic update from web-platform-testsHTML: no longer depend on SVGElement in IDL
See https://github.com/whatwg/html/pull/3671.
--
wpt-commits: fcf42b610c3eec811dc26a09b1404300aeb01ac1
wpt-pr: 10879
Automatic update from web-platform-testsDOM: retarget relatedTarget
relatedTarget gets retargeted. Also use test rather than async_test if possible.
Fixes#10854.
--
wpt-commits: b9f5402f16fa98c88428dace0a7088ef9dae8df3
wpt-pr: 10863
Automatic update from web-platform-tests[KeyboardMap] Initial stub for navigator.keyboard.getLayoutMap
This includes the WebIDL defs, initial WebPlatformTests and mojom
over to stubs in the RenderWidgetHost.
Spec: https://wicg.github.io/keyboard-map/
A proper implementation for this API will be in follow up cls,
a separate cl per platform.
Bug: 832811
Change-Id: I17dee21095665739a3f1986e48a2182d6b6fab00
Reviewed-on: https://chromium-review.googlesource.com/1014244
Commit-Queue: Gary Kacmarcik <garykac@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Scott Violet <sky@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556639}
--
wpt-commits: d9587de4ff827d75fefbd72f42e834078094202d
wpt-pr: 10495
Automatic update from web-platform-tests[Picture-in-Picture] Resolve promises when window is created and closed.
This makes the promise returned by enterPictureInPicture() resolved only
when window is created. Picture-in-Picture window size is still
hard-coded though and will be fixed in a future CL.
This also makes the promise returned by exitPictureInPicture() resolved
only when window is closed.
Bug: 806249
Change-Id: I8232a42a50b808527560eb0e6a69d8fb98da63e4
Reviewed-on: https://chromium-review.googlesource.com/1025832
Reviewed-by: Frank Liberato <liberato@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: apacible <apacible@chromium.org>
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/master@{#556567}
--
wpt-commits: 6d541700e3dca7a46672f440afcbba225930b648
wpt-pr: 10604
Automatic update from web-platform-testsAllow 0% in font-stretch
Per https://github.com/w3c/csswg-drafts/issues/2591, 0% should be an
allowed value in font-stretch. Remove the check that percentages are >=
0 for font-stretch, as any negative non calc values are already rejected
by kValueRangeNonNegative. Also update a test of valid calc values in
font-stretch, as even though they are outside the allowed range, they
should not be subject to parse-time constraints.
Bug: 834236
Change-Id: I0e728d8cc89b45bac7be956a7662533d4775c511
Reviewed-on: https://chromium-review.googlesource.com/1046926
Commit-Queue: Chris Nardi <cnardi@chromium.org>
Reviewed-by: Dominik Röttsches <drott@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556568}
--
wpt-commits: bbb732773d07230e07f95c551e09b851d450effa
wpt-pr: 10866
Automatic update from web-platform-testsAdd web platform tests for the new client hints
Add tests for "rtt", "downlink" and "ect".
Bug: 835333
Change-Id: If54c01612f10e96f7b37868e19b01a7ff3266d43
Reviewed-on: https://chromium-review.googlesource.com/1045917
Reviewed-by: Robert Ma <robertma@chromium.org>
Reviewed-by: Ryan Sturm <ryansturm@chromium.org>
Commit-Queue: Tarun Bansal <tbansal@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556532}
--
wpt-commits: 6f03878da8255e23699c5d45e98dd123ef88383a
wpt-pr: 10874
Automatic update from web-platform-testsOverride 'touch-action' for 'vertical-scroll'
With "vertical-scroll 'none'" as a feature set for an <iframe>, we want
to make sure the <iframe> cannot prevent the user from vertically
scrolling the page. One way of blocking user is to exclude "pan-y" from
"touch-action".
This CL makes sure that when an element is inside such frames, the
"touch-action" always includes "pan-y".
Link to explainer/design document:
https://docs.google.com/document/d/1qiWelnMlsOHuT_CQ0Zm_qEAf54HS5DhoIvEDHBlfqps/edit?usp=sharing
Bug: 611982
Change-Id: Ie60c665de3c82ec2438bcea10f56b54d51084eda
Reviewed-on: https://chromium-review.googlesource.com/1014389
Commit-Queue: Ehsan Karamad <ekaramad@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Jonathon Kereliuk <kereliuk@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556484}
--
wpt-commits: 549a93f3aa84166e5df3400cb53b35aa84f383e8
wpt-pr: 10718
Automatic update from web-platform-testsUpdate WPT test: url-in-tags.window.js
The web-platform-test: FileAPI/url/url-in-tags.window.js relies on the
load event to be dispatched after the page has scrolled to the anchor.
This is not guaranteed. It is currently non-deterministic in Chrome.
The page: https://scrolly-in-onload-event.glitch.me/ shows a case where
the opposite happens.
Doing task https://crbug.com/831155 caused this test to fail.
Note: This test was working only on Chrome.
Current status: https://wpt.fyi/FileAPI/url/url-in-tags.window.html
There is a chance applying this patch will make it work on Safari as
well.
Related CL:
https://chromium-review.googlesource.com/c/chromium/src/+/1042191
Bug: 831155
Change-Id: Ifa3f8e3d35cdb2635261248c3c9e9fd959f44340
Reviewed-on: https://chromium-review.googlesource.com/1046596
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556479}
--
wpt-commits: d353ff8898fdbb0e9d909c081d1a42d67e75b804
wpt-pr: 10864
Automatic update from web-platform-tests[css-grid] Avoid layouts during intrinsic size computation
The definition of intrinsic size excludes explicitly performing layouts
to compute the final value. However, it may be necessary to laid out
some children to retrieve accurate information about the geometry of
the box, specially when some of these children are orthogonal to the
box its intrinsic size is being computed.
However, the writing-mode specification suggest [1] that auto-sized
orthogonal boxes may require to run their sizing phase before any
content contribution could be established.
The Blink engine discourages performing layouts during intrinsic size
computation. In order to address the orthogonal flow issues and get
a more accurate sizing, both during intrinsic size and layout phases,
the engine performs a pre-layout of all the orthogonal boxes in the
layout tree (LocalFrameView::LayoutOrthogonalWritingModeRoot).
However, this pre-layout operations doesn't make sense for grid items
because the grid areas, the grid items' actual containing blocks, are
not computed yet. Hence, we decided to exclude grid items from this
pre-layout operation (PrepareOrthogonalWritingModeRootForLayout).
With this CL, we follow the same plan Blink has for orthogonal flow
boxes, but doing it once the grid items are placed in their
corresponding grid areas. Since the grid tracks sizing algorithm has
not been run at this stage, the size of the grid areas is estimated
based on the track's max-sizing function, in a similar way [2] the
algorithm does to deal with orthogonal items during the layout phase.
This change is covered by current tests, however, added an additional
test to verify we use the max-track sizing as a way to estimate the
orthogonal item's block-axis size.
[1] https://www.w3.org/TR/css-writing-modes-3/#orthogonal-flows
[2] https://drafts.csswg.org/css-grid/#algo-overview
Change-Id: I836b92120825916324f94befec6d35263ec84f2b
Reviewed-on: https://chromium-review.googlesource.com/1027882
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#556469}
--
wpt-commits: a878a9a9a5d1f4b0160620ba5479ba2c7d2e2373
wpt-pr: 10810
Automatic update from web-platform-testsAdds a test for basic WebRTC video codec conformance.
This tests that the browser conforms to RFC 7742, "WebRTC Video
Processing and Codec Requrements".
It establishes a new subdirectory for protocol-related WebRTC tests.
Bug: chromium:839753
Change-Id: Ia4795c4532fb74ae76e6a47329a41807479113c5
Reviewed-on: https://chromium-review.googlesource.com/1043886
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#556454}
--
wpt-commits: 644351d8f6c20a562f5d34dcbbb4f3ea416fadcf
wpt-pr: 10841
Automatic update from web-platform-testsAdd annevk to dom/OWNERS
I should probably help out here.
--
wpt-commits: d46cd6b9827d56c4cd380ea4ffa005df265c98a6
wpt-pr: 10869
