This updates the gitignore implemenation to take input like os.walk
but with additional stat data for the files. It also makes several
useful optimistaions:
* Avoid using regex when just matching a literal
* Identify patterns that can only match the final component of a path
and run those against that component rather than the full path.
* Add the possibility of providing a dictionary of paths to gitignore
statuses as a cache.
This dramatically reduces the amount of time we spend in gitignore
processing when updating the manifest.
Depends on D8223
Differential Revision: https://phabricator.services.mozilla.com/D8224
--HG--
extra : moz-landing-system : lando
We end up with a lot of rules like (?:.*)/.*\.ext which are basically
trying to find the last component in a path and match against
that. These are rather slow to run so the easiest thing tdo is just
pass in the last component of the path when we know that's the only
thing the rule can match.
The changes to surrounding code to use this API will be made in future
commits.
Depends on D8222
Differential Revision: https://phabricator.services.mozilla.com/D8223
--HG--
extra : moz-landing-system : lando
- Expose FetchEvent.resultingClientId on non-subresource, non-"report"-destination requests.
- Delay Clients.get(FetchEvent.resultingClientId) resolution until the resulting client is execution ready.
- Add WPTs to test for existence of resultingClientId and Clients.get promise resolution values.
Differential Revision: https://phabricator.services.mozilla.com/D5333
--HG--
extra : moz-landing-system : lando
This patch introduces 2 new prefs:
- devtools.console.stdout.chrome: if true, console API writes on stdout when
used by chrome code
- devtools.console.stdout.content: console API write on stdout when used by
content code.
Vendored robustcheckout extension from the version-control-tools
repository revision d78e5c52a0228c3dc8ed03fe43bf749c8e68bd20 without
modifications.
This is needed to support Mercurial 4.8.
Differential Revision: https://phabricator.services.mozilla.com/D11398
--HG--
extra : moz-landing-system : lando
Bug 1506643 disabled the usage of "about:newtab". But it's
actually needed by awsy for testing the memory consumption
of Firefox.
Differential Revision: https://phabricator.services.mozilla.com/D11932
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-testsRe-plumb backdrop-filter through blink-gen-property-trees
With this CL, backdrop-filter will continue to work when the
--enable-blink-gen-property-trees flag is enabled. Behavior should be
identical to behavior without the flag.
Also, I added a number of layout/WPT tests for backdrop-filter,
some of which currently pass, and some of which need fixing. The ones
that need fixing have been added to TestExpectations. These new tests
should reproduce (at least) these issues:
- https://crbug.com/314867 - respecting isolation
- https://crbug.com/525099 - respecting isolation
- https://crbug.com/547937 - border radius
- https://crbug.com/524689 - filter plus backdrop-filter
- https://crbug.com/745012 - boundary effect problems
I also moved the existing tests out of external/wpt/css/css-filter
into external/wpt/css/filter-effects, where they really should be,
now that filter-effects is being pulled into the tree.
Bug: 497522,314867,525099,547937,524689,745012
Change-Id: I2be33fbc0e17dec2cd138f9796971fb4a9a57216
Reviewed-on: https://chromium-review.googlesource.com/c/1316661
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607447}
--
wpt-commits: e1bde44cb56120f187d326557a681f87b31b43af
wpt-pr: 14008
--HG--
rename : testing/web-platform/tests/css/css-filter/blur-clip-stacking-context-001.html => testing/web-platform/tests/css/filter-effects/blur-clip-stacking-context-001.html
rename : testing/web-platform/tests/css/css-filter/blur-clip-stacking-context-002.html => testing/web-platform/tests/css/filter-effects/blur-clip-stacking-context-002.html
rename : testing/web-platform/tests/css/css-filter/blur-clip-stacking-context-ref.html => testing/web-platform/tests/css/filter-effects/blur-clip-stacking-context-ref.html
rename : testing/web-platform/tests/css/css-filter/filtered-block-is-container-ref.html => testing/web-platform/tests/css/filter-effects/filtered-block-is-container-ref.html
rename : testing/web-platform/tests/css/css-filter/filtered-block-is-container.html => testing/web-platform/tests/css/filter-effects/filtered-block-is-container.html
rename : testing/web-platform/tests/css/css-filter/filtered-html-is-not-container-ref.html => testing/web-platform/tests/css/filter-effects/filtered-html-is-not-container-ref.html
rename : testing/web-platform/tests/css/css-filter/filtered-html-is-not-container.html => testing/web-platform/tests/css/filter-effects/filtered-html-is-not-container.html
rename : testing/web-platform/tests/css/css-filter/filtered-inline-is-container-ref.html => testing/web-platform/tests/css/filter-effects/filtered-inline-is-container-ref.html
rename : testing/web-platform/tests/css/css-filter/filtered-inline-is-container.html => testing/web-platform/tests/css/filter-effects/filtered-inline-is-container.html
Automatic update from web-platform-testsHTMLScriptElement text attributes modified to accept TrustedTypes
HTMLScriptElement::text() and setText() functions modified to accept
TrustedScript as an argument.
Added HTMLScriptElement::innerText and HTMLScriptElement:textContent
attributes to override existing implementations in HTMLElement
and Node, and to accept TrustedScript.
Changed HTMLElement::innerText and Node::textContent .idl definitions
and adjusted setters and getters to accept TrustedScript.
Bug: 739170
Change-Id: I63da5714ffac328c6ae2f76e5da58c05f44a1cbf
Reviewed-on: https://chromium-review.googlesource.com/c/1178046
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607232}
--
wpt-commits: 860091dbc783a678f128328646a519d9891f0838
wpt-pr: 12531
Automatic update from web-platform-testsAdd unit tests for wrapper handlers in tools/serve
Add unit tests for all kinds of wrapper handlers in tools/serve/serve.py.
See #12452
--
Update the unit tests
* Fix the import error
* Improve the code style
--
Read and write files in binary mode
Read and write files in binary mode so the unit tests can pass in
Python3 environment.
--
wpt-commits: 2225031efc850d3b87ea33210b79730b466f5c50, dfbb0fd0cba67a8b0ea261fcfaaa805fe6ed7f03, d0c94e610154d3a7cdf1f2882a7ac74d4dfe3114
wpt-pr: 14004
Automatic update from web-platform-testsSet orphans and widows to 1 in new multicol test.
The test left orphans / widows at their initial value (2), but did
assume that we could freely break wherever we wanted. Blink honors
orphans and widows requirements inside multicol containers, so set
them to 1, to get the behavior that the test expects.
Bug: 904263
Change-Id: Ia138da5c65b1c5da450441f38e033320bc983a94
Reviewed-on: https://chromium-review.googlesource.com/c/1331389
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607211}
--
wpt-commits: 0d4f539f5d4c7272c9fe07bd204674b207e4a979
wpt-pr: 14021
Automatic update from web-platform-testsTypo: "opoacity" should be "opacity" (#14018)
--
wpt-commits: 2f868fae5b43c68e4807f6a4ec9487f13ea39cf4
wpt-pr: 14018
Automatic update from web-platform-testsMIME types: test 0x0B, 0x0C, and newlines
For https://github.com/whatwg/mimesniff/pull/90.
--
wpt-commits: 6aeb68e38a61c2e332a7592f5cad640cf58b73f2
wpt-pr: 13615
Automatic update from web-platform-tests[css-text] Advance width of a tab must be at least 0.5ch
Relates to https://github.com/w3c/csswg-drafts/issues/2883
--
Merge pull request #13336 from frivoal/text-2883
[css-text] Advance width of a tab must be at least 0.5ch
--
wpt-commits: 3e89195978753b5e77a4aa04b420d17eb20dddd8, 67fe8ce363b1e2981d322e0a1a10186062e26e64
wpt-pr: 13336
Automatic update from web-platform-testsRemove ES6 object matching shorthand notation from WebDriver tests (#14015)
This change is to allow older user agents that do not support ES6
constructs to run the WebDriver tests.
--
wpt-commits: fc1a5b73230225faf32bfb85f3928ce154211b0a
wpt-pr: 14015
Automatic update from web-platform-testsSnap at ScrollIntoView.
According to the spec,
https://github.com/w3c/csswg-drafts/issues/2593#issuecomment-386154394
scrollIntoView should
1) Always snap to the target element's snap alignment, and
2) All the affected scrollers should also land on a snap position if
one exists.
This patch does part 2). Before a scrollable_area is added to
the smoothScrollSequencer with its new scroll_offset, we will check if
it has a valid snap offset around, and update the final offset
accordingly.
We'll implement part 1) in a separate patch.
Bug: 842317
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_slimming_paint_v2;master.tryserver.blink:linux_trusty_blink_rel
Change-Id: Ica22134ed0b1f9d36f5a017c8dd0be54e907dd3d
Reviewed-on: https://chromium-review.googlesource.com/c/1188746
Reviewed-by: David Bokan <bokan@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#607019}
--
wpt-commits: a0610cf468e6208e74b2cfda77a565ab90fbd74e
wpt-pr: 13038
Automatic update from web-platform-testsgrid-template-areas serialization
strings in grid-template-areas are normalized, e.g. collapsing
whitespace to a single space, and collapsing repeated periods ('.')
to a single period.
https://github.com/w3c/csswg-drafts/issues/3261#issuecomment-436828363
--
Merge pull request #13977 from ewilligers/grid-template-areas-serialization-2
grid-template-areas serialization
--
wpt-commits: da90a07f543e3307b53230a1f0a2e8b6dc72b42b, a27659a86371bb2d98e622f4e57b85a546898ade
wpt-pr: 13977
Automatic update from web-platform-testsNEL: Generate reports in HTTPNetworkTransaction
Piece by piece, we are moving the Reporting and NEL processing code from
URLRequest and friends into HTTPNetworkTransaction, to make sure that we
produce reports for network requests as defined by the spec.
This patch moves the generation of the actual NEL reports, and includes
some new WPT test cases that verify that we create reports correctly for
redirects and cached responses.
TBR=msramek@chromium.org
Bug: 895823
Change-Id: Ie8e17a2a2b3571a7cdfd39057da486f5ad2c9f6f
Reviewed-on: https://chromium-review.googlesource.com/c/1318169
Commit-Queue: Douglas Creager <dcreager@chromium.org>
Reviewed-by: Misha Efimov <mef@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606958}
--
wpt-commits: 9902fbae9124fb565389983e49235d82cf429242
wpt-pr: 14007
Automatic update from web-platform-testsbrowser.py code cleanup
Some code cleanup that was recommended in https://github.com/web-platform-tests/wpt/pull/13185
--
wpt-commits: 7c568fdbd98ccdb92152c14521d3cc8c729a45a2
wpt-pr: 13239
Automatic update from web-platform-testsAdd a wpt create command
wpt create makes a file with the required elements for a test, and
optionally opens it in an editor.
--
wpt-commits: 726725be8f98607d521632e595fe5f2054570158
wpt-pr: 13701
Automatic update from web-platform-testswebkitRelativePath preserves common ancestors (#13988)
Drop requirement that webkitRelativePath only provides the shortest common ancestor, which matches behavior in Edge/Safari/Firefox, and soon Chrome.
Spec change: e6b848f4dc
Tracking issue: WICG/entries-api#18
--
wpt-commits: 378b79a9cd09df75403d88828d1793bb720a9488
wpt-pr: 13988
Automatic update from web-platform-testsWire the resizeMode property to the constraints parsing mechanism.
This CL adds resizeMode support for MediaStreamTrack.getConstraints()
and marks resizeMode as a supported constrainable property.
Support for getUserMedia(), applyConstraints() and getCapabilities()
will be added in follow-up CLs in this series.
Intent to Ship:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/V2srjdzRCXE
Bug: 854980
Change-Id: Ia23b8119768ab67ab498f0f8e2267aeb388f9fc3
Reviewed-on: https://chromium-review.googlesource.com/c/1309749
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606856}
--
wpt-commits: 055077093043d235040d20ae60458ee5ac6cded5
wpt-pr: 13846
Automatic update from web-platform-testsSetup logging earlier in the wpt run startup.
Curerntly we wait until we're setting up wptrunner kwargs to create the logger.
But that's pretty silly; we should set up the logger first thing and then use it
consistently to log during the setup phase.
--
wpt-commits: 47f0061f15dd2973dab11d87c03f0c8264d32e02
wpt-pr: 13578
Automatic update from web-platform-testsDo not send old capabilities to ChromeDriver
The configuration for Chrome currently sends 'platform' and 'version'
capabilities to ChromeDriver. These capabilities are non-standard and
unnecessary, and will cause errors when ChromeDriver becomes more
standard compliant.
--
wpt-commits: 7d9070444977a83af886d73bf80d57096be70ca5
wpt-pr: 13995
Automatic update from web-platform-testsFetch: CORS and request's Content-Type header
For https://github.com/whatwg/fetch/pull/829.
--
wpt-commits: eed621bc2f995bced9481df2cead4c4632c72cdd
wpt-pr: 13921
Automatic update from web-platform-testshtml: Fix a sanitization issue of type-change-state.html
type-change-state.html assumed sanitized value for " foo\rbar " was
fixed per a input type, and it was specified by 'sanitizedValue' field.
However, it depends on the previous type. For example, the new input
types of the following A and B are same, initial value setter arguments
are same, but sanitized values of A and B should be different due to the
sanitizer difference between 'hidden' and 'url':
A)
input.type = "hidden";
input.value = " foo\rbar ";
// input.value is " foo\rbar "
input.type = "text";
// input.value is " foobar ".
B)
input.type = "url";
input.value = " foo\rbar ";
// input.value is "foobar"
input.type = "text";
// input.value is "foobar".
This CL fixes this issue by replacing 'sanitizedValue' field with
'sanitizer' field, which specifies a simple sanitizer implementation.
This fixes five test cases, which have failed with all major browsers.
Change-Id: I1b5f75e610138b1d117e93723471427ee655c300
Reviewed-on: https://chromium-review.googlesource.com/c/1326203
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606730}
--
wpt-commits: 3cd60908e05beed166359907018c2abe238cb205
wpt-pr: 13993
Automatic update from web-platform-tests[media] Treat cross-origin redirect as TAINTED only for no-cors requests
With https://crrev.com/a9cbaa7a40e2b2723cfc2f266c42f4980038a949,
WebMediaPlayer blindly treats a resource experiencing cross-origin
redirects as TAINTED. In fact, it should be treated as TAINTED only
when its request mode is "no-cors".
The added tests are provided by hongchan@chromium.org.
Bug: 899745, 901383
Change-Id: Idb66407552085b053818f3e4a9d8d5ff3ddeaf45
Reviewed-on: https://chromium-review.googlesource.com/c/1325281
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Reviewed-by: Fredrik Hubinette <hubbe@chromium.org>
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606681}
--
wpt-commits: d5be80a86d4f938250c075ac12414ad47516969c
wpt-pr: 13980
Automatic update from web-platform-testsReland "Make XR FrameData and Environment mojo associated"
This is a reland of 126a1168e3bcffb43c706822b3aa28695840310f
The fix in this change addresses compile errors on the
Oculus platform.
TBR=dcheng@chromium.org
dcheng@chromium.org: please review, though there are no
new changes to vr_service.mojom
Original change's description:
> Make XR FrameData and Environment mojo associated
>
> The XRFrameDataProvider now returns an associated
> XREnvironmentDataProvider interface so that the
> two share callback queues and thus allow strict
> ordering of the two interfaces. This is critical
> for frame synchronization between frames and the
> associated environment data.
>
> Note: We can't just mark the interfaceptrs for
> XRFrameDataProvider and
> XREnvironmentIntegrationProvider as associated
> in the XRSession struct. XRDevice implementations
> mostly live on separate threads from the
> XRFrameDataProviders, so we'd have extra thread
> hopping. For the VR headsets we explicitly live
> off the main thread to avoid latency, and because
> we do some work that may block the thread the
> XRFrameDataProvider lives on (for example waiting
> for vsync, or submitting frames to headset APIs).
>
> Bug: 867057, 876135, 843376
> Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30
> Reviewed-on: https://chromium-review.googlesource.com/c/1171794
> Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Bill Orr <billorr@chromium.org>
> Reviewed-by: Klaus Weidner <klausw@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605545}
Bug: 867057, 876135, 843376
Change-Id: If76578ebabbb40d03a21f6f557c5d4c27f69fc38
Reviewed-on: https://chromium-review.googlesource.com/c/1324089
Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606643}
--
wpt-commits: a516e7edca11e2efe462d2bfc83b5b88dd9f4072
wpt-pr: 13969
Automatic update from web-platform-testsThe computed value of float with absolute positioning when there is no box should be "none" (#13958)
https://github.com/w3c/csswg-drafts/issues/1436
--
wpt-commits: 4477b9d2fadaca4314a9fc7d88ab6db6ad47a321
wpt-pr: 13958
Automatic update from web-platform-testshtml: Fix an issue of type-change-state.html about selectionDirection="none"
type-change-state.html contains assertions for the following operation in [1]:
> ..., and set its selection direction to "none".
However it had an issue that the assertions checked if
input.selectionDirection was "none". According to [2],
input.selectionDirection can be "forward" on specific platforms.
> update the element's selection direction to the given direction, unless
> the direction is "none" and the platform does not support that direction;
> in that case, update the element's selection direction to "forward".
[1] https://html.spec.whatwg.org/multipage/input.html#the-input-element:set-the-selection-direction
[2] https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#set-the-selection-direction
Change-Id: Idc1a97fbb2036e351a788a1f758b3239308d8c71
Reviewed-on: https://chromium-review.googlesource.com/c/1322264
Reviewed-by: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606310}
--
wpt-commits: 603b17f321fe4275050c59c87b1f3a29a33e9c96
wpt-pr: 13978
Automatic update from web-platform-tests[streams] Add tests for aborting pipeTo()
Add tests for aborting ReadableStream.prototype.pipeTo using an
AbortSignal.
Tests correspond to PR whatwg/streams#744.
--
wpt-commits: 349d41838068164e37a1cbd1c8c6ffeba4c72177
wpt-pr: 13358
Automatic update from web-platform-testsWindow onerror is not triggered bug fix
As pointed out in the bug, unhandled errors on worker threads were not
properly being propagated for the parent thread to handle as the spec
requires (https://html.spec.whatwg.org/multipage/workers.html#runtime-script-errors-2).
This fix adds in the code to do that.
Bug: 685303
Change-Id: Ie3e7ec03153a43efdc6e70b874d6b1a1d8ac35ef
Reviewed-on: https://chromium-review.googlesource.com/c/1287208
Commit-Queue: Katie Dillon <kdillon@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605857}
--
wpt-commits: 920e3b1051f7bcb1fff98417cf91c904dbbdd36a
wpt-pr: 13691
Automatic update from web-platform-testswebkit: add support for the WPE port (#13863)
WPE port is closely related to the GTK port, using the same WebDriver
implementation as well as similar testing-purpose browser application.
Much of the capabilities dictionary construction can thus be the same.
--
wpt-commits: 89692eac0360247e56ba1ae4c32ea38cf1b6a9a0
wpt-pr: 13863
Automatic update from web-platform-testsEnsure that lone surrogates don't appear in wptreport json (#13828)
Python will happily handle "string" data containing codepoints in the surrogate
range. In the JSON output these are always escaped and appear as \uD800 or
similar. That's pretty unfortunate for interop since other languages don't
necessarily support such codepoints not representing a character in the
unicode set in their normal string type. Although it's possible to clean this
up on import it seems more reasonable to ensure that our primary interchange
format is unicode-clean. Therefore this change starts escaping lone surrogates
using the U+ notation so that \uD800 becomed U+D800.
Because Python, this requires two implementations. In UCS4 Python we know that
only lone surrogates should appear in string data; characters outside the BMP
will be represented as a single internal character (*technically* this is
untrue since someone may manually create a string containing a sequence of
surrogates that happens to form a pair; we don't care about handling this
case other than as two unpaired surrogates that happen to be adjacent). In
UCS2 Python surrogates appear in the string data literally, so we need to
check each time we encounter one whether it's a low surrogate followed by
a high surrogate and not escape in that case.
--
wpt-commits: 275904c8b770d10a9d67f6786b75dd4461a9a932
wpt-pr: 13828
Automatic update from web-platform-testsupdate wpt feature policy tests, making them long tests
Bug: 829921
Change-Id: Ia2c70c62d4a4235b21996bbd185746080e1efa35
Reviewed-on: https://chromium-review.googlesource.com/c/1320010
Reviewed-by: Robert Ma <robertma@chromium.org>
Commit-Queue: Luna Lu <loonybear@chromium.org>
Cr-Commit-Position: refs/heads/master@{#606045}
--
wpt-commits: 1a7cb3deb6c8661e4cf245a7ffc3e324fb6795f2
wpt-pr: 13954
Automatic update from web-platform-testswebkit: provide port name as run info (#13862)
For the WebKit product, include the port name inside the run info, under the
'webkit_port' key. This will come in handy when disabling tests in metadata files
for specific ports.
--
wpt-commits: 9b9cf22d132ce60af8ad1801fd347965a1a96bae
wpt-pr: 13862
Automatic update from web-platform-tests[ci] Complete Docker image update (#13960)
A recent patch updated the Docker image used by Taskcluster when
building the project's `master` branch [1]. Update the corresponding
configuration for tasks triggered by pull requests. This improves parity
between the two processes, and because the new image is based on a more
recent LTS release of Ubuntu, it reduces the likelihood of errors due to
outdated system dependencies.
[1] https://github.com/web-platform-tests/wpt/pull/13676
--
wpt-commits: 3b729257c88fc09f200993317b6b84c9ae0aee3b
wpt-pr: 13960
Automatic update from web-platform-tests[Azure Pipelines] Document "Build pull requests from forks of this repository" (#13952)
--
wpt-commits: e0e8196c242c8fb1d2a62c13f23455a9d03bd4bb
wpt-pr: 13952
Automatic update from web-platform-tests[filter-effects] Parsing of backdrop-filter (#13871)
Test parsing, serialization and computed value for backdrop-filter
https://drafts.fxtf.org/filter-effects-2/#BackdropFilterProperty
--
wpt-commits: 208508bfdb7a8a9692394488bec2237102e16962
wpt-pr: 13871
Automatic update from web-platform-tests[LayoutNG] Fix vertical-align: text-top in quirks mode
When in quirks mode and there are no text siblings; e.g.:
<div><img><span>text</span></div>
and 'vertical-align: text-top' applied to <img> hits
DCHECK failure and results in incorrect position.
The test ensures that results are the same with the standard
mode.
Bug: 901123
Change-Id: I30564c66d5847f09caf3672ba3d456c0eb798d3e
Reviewed-on: https://chromium-review.googlesource.com/c/1320529
Commit-Queue: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605965}
--
wpt-commits: 48c278aad9f1570f14e47472e7cf304865602192
wpt-pr: 13962
Automatic update from web-platform-testsfix video reference in webvtt rendering tests
--
wpt-commits: c94bfaa0f97be784245d5c5405ebf2cae78df2f7
wpt-pr: 13553
Automatic update from web-platform-testsFix RTCRtpTransceiver direction tests (#13914)
* Update RTCRtpTransceiver setDirection to direction setter
* Fix currentDirection in RTCRtpTransceiver-direction.html
* Add negative test for setDirection
--
wpt-commits: d37a815dbca209eafc8eb71cb59ce59f4e66f975
wpt-pr: 13914
Automatic update from web-platform-testsRemove support for supportedTypes in Payment Request (#13858)
--
wpt-commits: 615bb572c95add74ca4fb9fed4af5269a49cf4ef
wpt-pr: 13858
Automatic update from web-platform-testsAdded mechanisms for default policy
With a default policy defined, assignments implicitly call createXXX on the default policy
Added ScriptState* to the accessors visible from JavaScript
Tests were updated to check string assignment when trusted-types are needed before and after the default policy is defined
Bug: 739170
Change-Id: I9bb841d69f324b841602d41abd71f753a9858af8
Reviewed-on: https://chromium-review.googlesource.com/c/1207530
Reviewed-by: Daniel Vogelheim <vogelheim@chromium.org>
Reviewed-by: Yuki Shiino <yukishiino@chromium.org>
Commit-Queue: Daniel Vogelheim <vogelheim@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605720}
--
wpt-commits: 24373750793a107c28dbfde50d61cfae192fb485
wpt-pr: 12952
Automatic update from web-platform-testsRun py36-flake8 also for tools/wpt/ (#13947)
--
wpt-commits: bfc7ce508b754e84e95830c2186f1fa8eb9f179e
wpt-pr: 13947
Automatic update from web-platform-testsRevert "Make XR FrameData and Environment mojo associated"
This reverts commit 126a1168e3bcffb43c706822b3aa28695840310f.
Reason for revert: Broke compile: https://logs.chromium.org/logs/chromium/bb/chromium.chrome/Google_Chrome_Win/39908/+/recipes/steps/compile/0/stdout
Original change's description:
> Make XR FrameData and Environment mojo associated
>
> The XRFrameDataProvider now returns an associated
> XREnvironmentDataProvider interface so that the
> two share callback queues and thus allow strict
> ordering of the two interfaces. This is critical
> for frame synchronization between frames and the
> associated environment data.
>
> Note: We can't just mark the interfaceptrs for
> XRFrameDataProvider and
> XREnvironmentIntegrationProvider as associated
> in the XRSession struct. XRDevice implementations
> mostly live on separate threads from the
> XRFrameDataProviders, so we'd have extra thread
> hopping. For the VR headsets we explicitly live
> off the main thread to avoid latency, and because
> we do some work that may block the thread the
> XRFrameDataProvider lives on (for example waiting
> for vsync, or submitting frames to headset APIs).
>
> Bug: 867057, 876135, 843376
> Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30
> Reviewed-on: https://chromium-review.googlesource.com/c/1171794
> Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
> Reviewed-by: Daniel Cheng <dcheng@chromium.org>
> Reviewed-by: Bill Orr <billorr@chromium.org>
> Reviewed-by: Klaus Weidner <klausw@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#605545}
TBR=dcheng@chromium.org,klausw@chromium.org,billorr@chromium.org,lincolnfrog@chromium.org
Change-Id: I7a2408629460f456bf1189acdb0837f7d22a7919
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 867057, 876135, 843376
Reviewed-on: https://chromium-review.googlesource.com/c/1318805
Reviewed-by: Dmitry Titov <dimich@chromium.org>
Commit-Queue: Dmitry Titov <dimich@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605551}
--
Merge pull request #13939 from web-platform-tests/chromium-export-0ef86cd598
Revert "Make XR FrameData and Environment mojo associated"
--
wpt-commits: 97ef8fa350d0b1cf5c4692a71b1040d66266e7b7, b306f085d1a008b7636b60efa67a5b89d1fc2f52
wpt-pr: 13939
Automatic update from web-platform-testsFix and re-enable simplecall-no-ssrcs.https.html.
With the changes, the test should pass regardless of if the Chrome or
Firefox behavior is used for what to do when no MSIDs are signaled.
Follow-up work is needed to test both the case of "a=msid:-" and no
"a=msid" line whatsoever, awaiting spec issue to be resolved:
https://github.com/w3c/webrtc-pc/issues/2027
// Relying on fippo's approval to land.
TBR=hta@chromium.org
Bug: 901711
Change-Id: Icaf089d206413510aadad54a0c10b2674450385a
Reviewed-on: https://chromium-review.googlesource.com/c/1319612
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605678}
--
wpt-commits: bce2269d0f17d2a89247895cbee21530ae83c96e
wpt-pr: 13950
Automatic update from web-platform-tests[presentation-api] Revise the test for reconnecting multiple presentations (#13196)
Test closing and reconnecting to multiple connections simultaneously
--
wpt-commits: 7a51b509430cc115df632608356999fa18ac4491
wpt-pr: 13196
Automatic update from web-platform-testswebrtc: rename DTLSTransport.transport to .iceTransport (#13915)
test for https://github.com/w3c/webrtc-pc/pull/2017
--
wpt-commits: c05700b258089fd547808c54707cdc3a64b48344
wpt-pr: 13915
Automatic update from web-platform-testsRemove the "W3C WebSocket API" prefix from websockets/ tests (#13478)
This prefix doesn't add any useful information, and isn't used in all
tests in this directory. Noticed because of the screen real estate it
takes up in a view like this:
https://wpt.fyi/results/websockets/Send-binary-65K-arraybuffer.any.html
In the directory, this command was run, on macOS:
git grep -lF 'W3C WebSocket API - ' | xargs sed -i '' 's/W3C WebSocket API - //g'
--
wpt-commits: 1e747acc90ecdbd23ef3348a144b77696cced55b
wpt-pr: 13478
Automatic update from web-platform-testsUpdate RTCPeerConnection-setRemoteDescription-tracks.https.html as MediaStream has no constraint on the order of the track (#13940)
--
wpt-commits: 89c900d2e2bae0592564dfc5bf06cc4b08b3cac5
wpt-pr: 13940
Automatic update from web-platform-tests[wptrunner] Convert data prior to transmission
A recent improvement to wptrunner modified the way data structures are
transmitted from the browser to the WebDriver server [1]. One
consequence of this change is that the data structures are created in a
JavaScript realm which differs from the realm in which the "Execute
Script" WebDriver command is running. As of version 17, Microsoft Edge
does not correctly serialize cross-realm values, so referenced
improvement unintentionally precluded testing in that browser.
Serialize and deserialize the results data structure from the realm of
the WebDriver command to avoid this problem.
[1] https://github.com/web-platform-tests/wpt/pull/13419
--
wpt-commits: e3738ec2754f0c3fb44a03af3104db1decf9fca7
wpt-pr: 13938
Automatic update from web-platform-testsXMLHttpRequest: manipulate Content-Type a little more
99f4fdcd906411c036e96c055e28b3e6ca84a1cc was not entirely correct unfortunately.
--
wpt-commits: 47aa8753bba8656899eca2e7c3851a7c75c1d2d7
wpt-pr: 13920
Automatic update from web-platform-testsChange the button type to int in the pointerActionSequence API
In order to match with test_driver Actions API, we need to change the
button type from string to int in the pointerActionSequence API and the
related web platform tests and layout tests.
Bug: 893480
Change-Id: I151849d31038cf40a2a603196e0f616e15d89072
Reviewed-on: https://chromium-review.googlesource.com/c/1297637
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Navid Zolghadr <nzolghadr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605605}
--
wpt-commits: 41f76e27e00de380d5a100aa0c1065fa202e9c0a
wpt-pr: 13933
Automatic update from web-platform-testsMake XR FrameData and Environment mojo associated
The XRFrameDataProvider now returns an associated
XREnvironmentDataProvider interface so that the
two share callback queues and thus allow strict
ordering of the two interfaces. This is critical
for frame synchronization between frames and the
associated environment data.
Note: We can't just mark the interfaceptrs for
XRFrameDataProvider and
XREnvironmentIntegrationProvider as associated
in the XRSession struct. XRDevice implementations
mostly live on separate threads from the
XRFrameDataProviders, so we'd have extra thread
hopping. For the VR headsets we explicitly live
off the main thread to avoid latency, and because
we do some work that may block the thread the
XRFrameDataProvider lives on (for example waiting
for vsync, or submitting frames to headset APIs).
Bug: 867057, 876135, 843376
Change-Id: If2fb62fcd185825209dec08e421df05f34d41c30
Reviewed-on: https://chromium-review.googlesource.com/c/1171794
Commit-Queue: Max Rebuschatis <lincolnfrog@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Bill Orr <billorr@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605545}
--
wpt-commits: 2ba8053bfa3946457355fa73d2873144fe4479d2
wpt-pr: 13764
Automatic update from web-platform-testsCope even better with the mess we leave behind after a continuation.
Tried to fix this in https://chromium-review.googlesource.com/c/1309777
but incorrectly assumed that bogus continuation chains were formed by
direct siblings. But they may also be arbitrary-level cousins. Need to
walk through all non-atomic inlines between one continuation object and
the next in the chain, to figure out whether there is an anonymous block
between two objects in the continuation chain. Only then should we
update the positionedness of anonymous blocks. Only perform this check
if positionedness changed, since it's not for free.
Bug: 901598
Change-Id: I3e49a4ce8081a4a3190cc1569480189cbcccdcc4
Reviewed-on: https://chromium-review.googlesource.com/c/1317627
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605465}
--
wpt-commits: fb4466fa28e359a770f6d7007a2a1302fec0c8a2
wpt-pr: 13919
Automatic update from web-platform-testsCorrect inherited feature policy when allow attribute is used.
This fixes an error in the inherited policy calculation where a frame
which was explicitly allowed to use a feature through the Feature-Policy
header would be blocked if the "allow" attribute was also present on
the iframe element.
The behaviour now matches the spec algorithm at
https://wicg.github.io/feature-policy/#define-inherited-policy-in-container
Tests have been added to catch this case.
Change-Id: I7a394202c615be3088fda738d7fc65f16bcadf34
Reviewed-on: https://chromium-review.googlesource.com/c/1293610
Reviewed-by: Luna Lu <loonybear@chromium.org>
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605431}
--
wpt-commits: d5f4dec283def0baeca6e5a88223dac67935e798
wpt-pr: 13717
Automatic update from web-platform-testsCSS: serialize pointer-events keywords in lower case
https://drafts.csswg.org/cssom/#serializing-css-values
"To serialize a CSS component value depends on the component, as follows:
keyword
The keyword converted to ASCII lowercase."
Bug: 901666
Change-Id: Iff579a363de13441c75bbebfc951095b071f6060
Reviewed-on: https://chromium-review.googlesource.com/c/1317300
Commit-Queue: Emil A Eklund <eae@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605383}
--
wpt-commits: f917e2dfc6649f9217f51dec9fd45eaef16188fc
wpt-pr: 13917
James Graham
Ahilya Sinha
Gurzau Raul
Armen Zambrano G.
Perry Jiang
Andrew McCreight
Margareta Eliza Balazs
Dragana Damjanovic
Geoff Brown
Andrea Marchesini
Mats Palmgren
Gregory Szorc
Bob Clary
Ionut Goldan
Henrik Skupin
Rob Wood
Andreea Pavel
Razvan Maries
Valentin Gosu
Sebastian Hengst
Gijs Kruitbosch
Kartikaya Gupta
Jonathan Kingston
Coroiu Cristina
Paolo Amadini
moz-wptsync-bot
Mason Freed
Daniel Vogelheim
qiuzhong
Morten Stenshorne
Antoine Quint
Joshua Bell
Anne van Kesteren
Florian Rivoal
Mark Roberts
jimevans
CYBAI
Sandra Sun
Mike Pennisi
autofoolip
Eric Willigers
Douglas Creager
Dominic Farolino
Guido Urdaneta
Luke Bjerring
John Chen
Kent Tamura
Yutaka Hirano
Max Rebuschatis
aestes
pyup.io bot
François REMY
L. David Baron
youennf
Adam Rice
Rayan Kanso
Žan Doberšek
Luna Lu
Geoffrey Sneddon
Philip Jägenstedt
Eric Willigers
Hiroki Nakagawa
Koji Ishii
Gary Katsevman
Youenn Fablet
Charles Vazac
Marcos Cáceres
Jan-Ivar Bruaroey
Dmitry Titov
Henrik Boström
Tomoyuki Shimizu
Philipp Hancke
Christian Bromann
Lan Wei
Francois Remy
Emircan Uysaler
Ian Clelland
Zhuoyu Qian