Automatic update from web-platform-tests
Don't stop text-decoration propagation at non-UA shadow boundaries.
There is no spec saying this should happen. Neither Gecko nor WebKit
does this, and it breaks devtools UX. We still need to stop propagation
into UA shadow trees to avoid text-decoration applying to media
controls, for instance.
Bug: 938193
Change-Id: I21895cb36b0d0bf2b39b42c000d3cf5ceb4255f1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1508097
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638571}
--
wpt-commits: a9dee916c907b7749a611848308708e9890dbfac
wpt-pr: 15718
Automatic update from web-platform-tests
Fix#15625: deal with Safari throwing when moving the window to (0,0) (#15659)
This is fixed in STP and likely will not persist beyond Safari 12.
--
wpt-commits: d1ef68162b8118fec533199c19f75aa27240318d
wpt-pr: 15659
Automatic update from web-platform-tests
Improve tainting for filter primitives
This makes tainting for many filter primitives less pessimistic, by
implementing the "Tainted Filter Primitives" section [1] from the
specification.
For feFlood/feDropShadow:
A value of 'currentcolor' for 'flood-color' taints.
For feSpecularLighting/feDiffuseLighting:
A value of 'currentcolor' for 'lighting-color' taints.
For the other primitives (which currently lack any specific logic), i.e:
feBlend, feComponentTransfer, feComposite, feConvolveMatrix,
feDisplacementMap, feGaussianBlur, feMorphology, feOffset and feTile
no local tainting is performed (the TaintsOrigin() override is returning
false).
The signature/convention of the TaintsOrigin() is changed by removing
the |inputs_taint_origin| argument, and always taint the
primitive if it (the flag returned by FilterEffect::InputsTaintOrigin)
is true. This saves each primitive to have to relate to this flag. (For
primitives that have no inputs this flag would always be false
regardless.) This means that TaintsOrigin() for each primitive is now
essentially computing the "local" tainting state.
[1] https://drafts.fxtf.org/filter-effects/#tainted-filter-primitives
Bug: 792518
Change-Id: Ie2d45eeb1ae8478009b88b8b87b3c4c325ede306
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1503257
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Reviewed-by: Philip Rogers <pdr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638546}
--
wpt-commits: 41a36beff1e1145e756f4c1d505ff7c67785f2af
wpt-pr: 15683
Automatic update from web-platform-tests
Exclude reftest_base types from the test tree.
--
Remove RefTestBase from the known item mappings.
--
wpt-commits: 4f64577312174deca261f5642c896ce33117fbf8, 405751fab6fec48b30c28bfa0f6b86fe056ee425
wpt-pr: 15709
Automatic update from web-platform-tests
Fix Acid2 to take the screenshot after loading & scrolling
--
Add a reference for Acid2 that should pixel-for-pixel match
Per https://bugzilla.mozilla.org/show_bug.cgi?id=343583#c6, Hixie
never intended the reference.png to match exactly (e.g., the nose
especially is quite fragile with anti-aliasing differences).
This is based on the test itself, but by and large just uses block
layout with pretty simple border/backgrounds. The only complexity is
in the eyes (where layering is needed to get the background
interpolated as on the test) and the nose (which mostly matches the
test as browsers trivially differ around the aliasing of
border edges).
--
wpt-commits: 8a28e1a47287265e54f3c28650f3201f6f3e7dff, 42330b2ea1aa9e8c23fb2fbcfcba9f8cabd9bb18
wpt-pr: 15677
Automatic update from web-platform-tests
Add support for AudioContextOptions sampleRate
Optional sampleRate parameter to AudioContextOptions, if provided then
the AudioContext will run at this sampleRate, otherwise it will run at
the hardware rate.
Running the AudioContext at a lower sample rate can allow running a
heavier graph on low-end devices, for example if a given device is able
to run with X nodes at a sample rate of 48k, it can support roughly
2X nodes at 24k or 4X nodes at 12k.
Bug: 432248
Change-Id: I835f28b4625763bd6a6ddbee9b89636ef8a8a066
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1482957
Reviewed-by: Kent Tamura <tkent@chromium.org>
Reviewed-by: Raymond Toy <rtoy@chromium.org>
Reviewed-by: Hongchan Choi <hongchan@chromium.org>
Commit-Queue: Andrew MacPherson <andrew.macpherson@soundtrap.com>
Cr-Commit-Position: refs/heads/master@{#638498}
--
wpt-commits: 9b994b36003246370b352fa70c563866a8443e4e
wpt-pr: 15520
Automatic update from web-platform-tests
service worker: registration-mime-types.https.html could be slow
Add a meta tag to have long timeout for the test.
This should deflake the test.
Bug: 937544
Change-Id: I87e0dda7647371e1082639037090264240a5bd06
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1506058
Commit-Queue: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638458}
--
wpt-commits: 553786e79703fe5bad735aefa5894ec26ccdf3c9
wpt-pr: 15712
Automatic update from web-platform-tests
Fix background-root-018-ref.xht to use same font size as test (#15670)
--
wpt-commits: 78f764c05c229883e87ad135c7153051a66e2851
wpt-pr: 15670
Automatic update from web-platform-tests
Fix hit-testing of nested clip-paths with objectBoundingBox units
A nested clip-path should resolve against the original elements
reference box, but it would instead resolve against the referencing
<clipPath>.
Pass the appropriate reference box to SVGLayoutSupport::IntersectsClipPath.
Took the opportunity to export some related tests to WPT.
Bug: 938913
Change-Id: I6d6ad88f0a97028b21b1f1a488afbdd42a96264b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1505949
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#638293}
--
wpt-commits: bc14d429b9ade658d33045261548c385eed585bc
wpt-pr: 15707
Automatic update from web-platform-tests
Remove unneeded call to isdir when updating the manifest in git (#15699)
In the clean manifest case, this is the majority of the cost of the
update nowadays.
--
wpt-commits: 1729d46c04df4a0ae173bde7a24dbbd5b3207378
wpt-pr: 15699
Automatic update from web-platform-tests
IndexedDB: Convert bindings-inject-key.html to promise-based
Update bindings-inject-key.html from an async test to promise-based.
This allows the test to run so that each subtest is run serially.
Patch by Joshua Bell <jsbell@chromium.org>.
Bug: 934844
Change-Id: If9834a35fcb964a6fe15776e3e091d326f3f8a0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1504458
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Chase Phillips <cmp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638268}
--
wpt-commits: 9da6dbfef1bc1fee23c7e7ce368a7263b4a9e6cd
wpt-pr: 15693
Automatic update from web-platform-tests
Add RefTestBase to mapping from manifest item name to class.
--
wpt-commits: 2ef72e51c5ec0dba55f26dae71d57f076d123750
wpt-pr: 15704
Automatic update from web-platform-tests
RTCError: Make "message" optional and be the last argument.
Based on https://github.com/w3c/webrtc-pc/pull/2112.
Bug: 937844
Change-Id: I7ad149f47fb394f15055cc8fd77e79b4e5e0f317
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1499613
Commit-Queue: Henrik Boström <hbos@chromium.org>
Reviewed-by: Marina Ciocea <marinaciocea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638192}
--
wpt-commits: e8831d9d354972a39ccfe388dd99eb5e2a6249a8
wpt-pr: 15651
Automatic update from web-platform-tests
[css-properties-values-api] Syntax string parser.
This CL implements the syntax string parser according to the new spec. The
parser operates on the "preprocessed input stream" described by css-syntax,
and while it reuses some algorithms used by the tokenizer, it does not
rely on actual tokens.
Overview of this CL:
* Added CSSSyntaxStringParser, which can parse the syntax string into
a CSSSyntaxDescriptor. Usage:
auto descriptor = CSSSyntaxStringParser("<color>").Parse();
* The previous syntax string parser functions were mixed together with
functions for parsing a token stream against a registered syntax, which
was a little confusing. Hence this CL splits the syntax string parsing
into a separate class.
* Moved a few parser algorithms from CSSTokenizer to css_parser_idioms,
to make them usable without a tokenizer.
* Unit tests: there is some overlap between the unit tests and WPT.
However, the unit tests can (and do) check the resulting internal
structure of the CSSSyntaxDescriptors, so they do add additional value
over just WPT.
R=futhark@chromium.org, ikilpatrick@chromium.org
Change-Id: I2d671ca0e58cd123a7809a24a4e83aec3883b175
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1503755
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638178}
--
wpt-commits: a5570d3f5c71ee02016e31746869622c638ced82
wpt-pr: 15696
Automatic update from web-platform-tests
[ElementTiming] Add request URL and responseEnd
This CL adds the initial URL and the response end from ResourceTiming
into ElementTiming. The information is currently only stored on the
ResourceTimingInfo object which is not accessible to ImageElementTiming
(and in fact, could be gone by the time the ElementTiming code is
executed). Thus, we store the information in ImageResourceContent.
Bug: 879270
Change-Id: I72a80c67956adb6e869f39ca3c77829bad86044e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1483733
Reviewed-by: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638153}
--
wpt-commits: 84bcab667e849b1baa6b0bd70244375190521b59
wpt-pr: 15554
Automatic update from web-platform-tests
[Animation Worklet] Remove unnecessary force composition
We used to have will-change: transform in test reference but they are
no longer needed.
Change-Id: Ib6870863760e32de201a0560fa59f43634c72da8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1504711
Commit-Queue: Yi Gu <yigu@chromium.org>
Reviewed-by: Xida Chen <xidachen@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638107}
--
wpt-commits: 665e6eac0fef14a35d453bfc9140fd8b6606f821
wpt-pr: 15694
Automatic update from web-platform-tests
[html] reflection.js should not test default values if customGetter is specified.
Bug: crbug.com/894661
Change-Id: I1df3af43ec2818f181eff99277c1d14c0dd3bb63
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1502772
Commit-Queue: Philip Jägenstedt <foolip@chromium.org>
Auto-Submit: Kent Tamura <tkent@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638102}
--
wpt-commits: 4eae01e09b96ba93c748148ed583b1f08d6eeb91
wpt-pr: 15668
Automatic update from web-platform-tests
HTML: escape CR character with 
 in canvas test
See https://github.com/web-platform-tests/wpt/pull/1599
--
wpt-commits: 48f22602a7c347fe2316a6769866b7871232f0ab
wpt-pr: 15685
Automatic update from web-platform-tests
Make -webkit-line-clamp respect line-height.
Previously the -webkit-line-clamp implementation didn't use the bottom
edge of the line-box, instead using the bottom of any content inside
it.
While simple in the old layout engine, this adds complexity for the
Firefox compat implementation, as well as an implementation on
LayoutNG.
Additionally Google front-end engineers are requesting we try and fix
this issue.
(see bug).
The added test relies on the implementation of text-overflow to behave
the same.
Bug: 937931
Change-Id: I3cac20dc79e2487da59cd28ac453f900d4898f21
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1495439
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638018}
--
wpt-commits: e4f29239c6feba2fc19bb254d99e8bf0c07c3913
wpt-pr: 15688
Automatic update from web-platform-tests
SignedExchange: Populate BodySize Resource Timing fields
Before this patch, encodedBodySize [1] and decodedBodySize [2] fields of
navigation / resource timing entry for Signed Exchanges were not
populated.
After this patch, these fields will have the sizes of Signed Exchange's
inner response body, before and after decoding mi-sha256 encoding.
[1] https://www.w3.org/TR/resource-timing-2/#dom-performanceresourcetiming-encodedbodysize
[2] https://www.w3.org/TR/resource-timing-2/#dom-performanceresourcetiming-decodedbodysize
Bug: 928589
Change-Id: I6b7800497e411822172dea4769ab8fc9d4955b53
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1496261
Commit-Queue: Kunihiko Sakamoto <ksakamoto@chromium.org>
Reviewed-by: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#638001}
--
wpt-commits: 4c1c9c9a0607c8c654c0af34f491d61ebc67c339
wpt-pr: 15615
Automatic update from web-platform-tests
[css-flexbox] If flex-basis is an indefinite %, don't use width/height
Instead, resolve it to auto (=logical height)
In the future, this codepath can also be used to implement
flex-basis: content.
Bug: 531656
Change-Id: I57f6cb60ca32919c3efda9e32bc68f524362526a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1490212
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#637973}
--
wpt-commits: a8c54846c26b4029ea253fad44cadc705af94c0b
wpt-pr: 15689
Automatic update from web-platform-tests
Upstream tests from fast/workers to external/wpt/workers.
This cl upstreams the tests that were translated in this cl:
https://chromium-review.googlesource.com/c/chromium/src/+/1475004
It also deletes some of the redundant tests in wpt/workers as a
result of the move.
Bug: 795636
Change-Id: Ic5678837dd9314c064f9e8a25bdb62468bfcb49f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1500938
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Katie Dillon <kdillon@chromium.org>
Cr-Commit-Position: refs/heads/master@{#637926}
--
wpt-commits: 810ec024edb749071534252c66c11ddd8afd5c48
wpt-pr: 15663
Automatic update from web-platform-tests
IndexedDB: Fix WPT bindings-inject-key to clean up Object.prototype
chromedriver doesn't allow changing Object.prototype to add enumerable
properties, but this test requires setting some values on
Object.prototype. When Object.prototype.a is set to:
{b: {c: 'on proto'}}
chromedriver fails with:
JavascriptErrorException: javascript error (500): Maximum call stack size exceeded
(Session info: chrome=72.0.3626.121)
Remote-end stacktrace:
#0 0x563ff3a32a59 <unknown>
#1 0x563ff39cb7f3 <unknown>
#2 0x563ff38fcd7c <unknown>
#3 0x563ff38ff78c <unknown>
#4 0x563ff38ff5f7 <unknown>
#5 0x563ff38ffbe7 <unknown>
#6 0x563ff38fff1b <unknown>
#7 0x563ff38a3f7a <unknown>
#8 0x563ff3899bf2 <unknown>
#9 0x563ff38a37b7 <unknown>
#10 0x563ff3899ac3 <unknown>
#11 0x563ff38782d2 <unknown>
#12 0x563ff3879112 <unknown>
#13 0x563ff39fe865 <unknown>
#14 0x563ff39ff32b <unknown>
#15 0x563ff39ff70c <unknown>
#16 0x563ff39d940a <unknown>
#17 0x563ff39ff997 <unknown>
#18 0x563ff39e9947 <unknown>
#19 0x563ff3a1a800 <unknown>
#20 0x563ff3a3c8be <unknown>
#21 0x7f3bf4545494 start_thread
#22 0x7f3bf2d58a8f clone
Ran 1 tests finished in 2.0 seconds.
• 0 ran as expected. 0 tests skipped.
• 1 tests had errors unexpectedly
Work around this problem by cleaning up the test environment so
Object.prototype no longer has the override by the time chromedriver
tries to inspect the test result.
While here, fix the other tests to use the t.add_cleanup() function
so they'll cleanup their test environment in case they exit in
some other way besides reaching t.done().
The underlying chromedriver issue is tracked upstream at
https://crbug.com/chromedriver/2555.
Bug: 934844
Change-Id: Id1b4ab2a908bfbc001e2a2d045eeec3ef01c24d9
--
wpt-commits: 1be74ca2738a05f6e8d98d55ba44c50e3a332554
wpt-pr: 15637
Automatic update from web-platform-tests
[css-flexbox] Don't always add the child as percentage-sized child
ComputePercentageLogicalHeight has the side-effect of calling
AddPercentHeightDescendant on the containing block; that is not great
when we just want to check if a size is definite, from
MainSizeIsDefiniteForPercentageResolution. Add a parameter to make it
optional.
Also change CrossAxisSizeIsDefinite over to this function. Here, we
do not have to worry about AddPercentHeightDescendant because we
will later resolve that size through normal mechanisms anyway.
Bug: 933931
Change-Id: Id44d15eb546c15bbdece99282550419eb0f8654e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1492294
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#637885}
--
wpt-commits: 0d35193f1d50bc3b6a83c3f6d78da2f267636983
wpt-pr: 15586
Anne van Kesteren
Rune Lillesveen
Sam Sneddon
moz-wptsync-bot
Fredrik Söderquist
Hiroshige Hayashizaki
Josh Matthews
Andrew MacPherson
autofoolip
Kenichi Ishibashi
kaixinjxq
rajendrant
Chase Phillips
Piotr Bialecki
Henrik Boström
Anders Hartvoll Ruud
Nicolás Peña Moreno
Yi Gu
Kent Tamura
Simon Pieters
Takayuki Sato
Ian Kilpatrick
Kunihiko Sakamoto
Christian Biesinger
Aleks Totic
kdillon