Automatic update from web-platform-tests
[webnfc] Remove incorrect tests (#17425)
Per spec https://heycam.github.io/webidl/#es-DOMString,
non string value will be converted to string via `toString()`
method, therefore there's no `TypeError` to be thrown.
--
wpt-commits: 3a00a57af5f449a72f0e1b89dae6f1bd15ad8fcd
wpt-pr: 17425
Automatic update from web-platform-tests
Worker: Remove duplicate service worker interception tests for shared workers
worker-interception.https.html has more test coverage, and is well-formatted.
Bug: n/a
Change-Id: I29640ffa781c1b90b1faa56eab4f771c1a3c0a84
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1669137
Auto-Submit: Hiroki Nakagawa <nhiroki@chromium.org>
Commit-Queue: Matt Falkenhagen <falken@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#671183}
--
wpt-commits: 982f12dc86098e5b32ffec455520a5eb114c27af
wpt-pr: 17414
Automatic update from web-platform-tests
[docs] Increase strictness of build process (#17401)
Use the `-W` flag to interpret Sphinx warnings as errors, causing the
build to fail in the presence of either. This makes various authoring
mistakes more visible. Perhaps most importantly: it highlights instances
of "orphaned" content.
Fix all details which were previously reported as warnings and thus
permitted.
--
wpt-commits: 9c6304b71c5ee090ebc1eef02ab32b70444d9704
wpt-pr: 17401
Automatic update from web-platform-tests
Allow var() references in -internal-visited-* properties.
Previously, -internal-visited-* properties didn't get any parsing behavior,
because they were assumed to be used during style application only. In
other words, it was assumed that the parsing would happen _before_ e.g.
color would expand to -internal-visited-color.
This is (of course) not true if the value has a var() reference, since
the actual parsing then happens computed-value time.
To fix this, this CL gives all -internal-visited-* properties parsing
behavior.
The "pending substitution value" adds complexity here, since the value
itself contains the shorthand it came from. This means that if e.g. the
border shorthand is parsed with a value that contains a var() reference,
the corresponding -internal-border-*-color property will point to the
same pending substitution value, that contains the "border" shorthand.
When resolving that pending substitution value computed-value time,
we expand the shorthand into its longhands, which of course are unaware
of the -internal-visited-* context. To fix this, this CL adds a way to
get the unvisited counterpart from a visited property, and uses the
unvisited CSSPropertyID as they key for the pending substitution cache.
Bug: 974665, 976913
Change-Id: I1a168bfe188eaccad7feac6c065f8e447ee56dbe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1669290
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670896}
--
wpt-commits: be93a1b93e08be1bd161208aaa6ab662c1c2d1c1
wpt-pr: 17411
Automatic update from web-platform-tests
WebSocket: stop removing an iframe in onerror from crashing
There was an issue that if the iframe owning a WebSocket was
synchronously removed in the onerror handler then it would crash the
render process. This was caused by unconditionally calling Close()
without checking the current state.
Fix it.
Also add a web platform test.
Bug: 974667
Change-Id: Iaeb8f96cf600a2c052f06b5b59f4444b02615e83
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1663681
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670061}
--
Set a long timeout
--
wpt-commits: 433e1f06259a79c6cb8bf695bc03ffdfdfe4e7e7, 28ad65497bccb301707e341a9d36f9d144e2793e
wpt-pr: 17380
Automatic update from web-platform-tests
Implement basic LargestContentfulPaint API
This CL adds a basic implementation of the LargestContentfulPaint API.
The implementation is done behind a flag, and is missing attribution
information and special handling for images.
Explainer: https://github.com/WICG/LargestContentfulPaint
Intent to Implement:
https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/WVqgYtyaGJk
Bug: 965505
Change-Id: Ic29604349dc60de2808bdef3df4684e81e1845d7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1646634
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670911}
--
wpt-commits: 93ba864d402d941a2670681d535e33723e5296c0
wpt-pr: 17214
Automatic update from web-platform-tests
Enable PauseExecutionContextOnBackgroundFreeze
Thie change enables (experimentally) pausing the execution context
when a document is frozen.
The WPT tests written required that promise resolution continued after
the page was frozen. This isn't the case when
PauseExecutionContextOnBackgroundFreeze is enabled so rewrite the tests
to poll for the correct state.
BUG=957589
Change-Id: If104235fd7281d88b5d86a3f0b89337828e7f4e7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662633
Reviewed-by: Shubhie Panicker <panicker@chromium.org>
Reviewed-by: Alexander Timin <altimin@chromium.org>
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670883}
--
wpt-commits: 81c649c98aa73ac14416491271ed001ffe9e4bbe
wpt-pr: 17363
Automatic update from web-platform-tests
[Azure] Fix logging params
This makes the logging behaviour consistent across all jobs on Azure:
info level tbpl logging to stdout, which is also consistent with
Taskcluster setup.
Notably, the previous configuration for "all tests: Edge" accidentally
specified --log-tbpl twice, causing duplicate log outputs, which is
fixed in this commit.
--
Disable version check of EdgeDriver
--
wpt-commits: 7dd31d2b2f9ebca522b50af958c18208d08683ae, 5303a4e841969e0b5991c45c276027a671e3ba20
wpt-pr: 17404
Automatic update from web-platform-tests
Refactor SRI script tests to prepare for Preload + SRI
This CL refactors the SRI script tests and what script resources they
consume to remove duplication, and factor out + generalize some of the
helpers, such as the script URL prefixes.
Before this CL, there were multiple script files whose contents were
irrelevant to the tests. The scripts would be served differently due
to `.headers` files. This CL consolidates all of the script resources
into a single `script.js` that the test runner can use while demanding
specific headers for tests. This file and factored-out URL prefixes in
`sri-test-helpers.sub.js` will be used by Preload + SRI tests, so this
CL makes writing those tests cleaner.
Bug: 677022
Change-Id: Ie6cc312f9d81de4d5f75925810b7ce88a61910a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1667326
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670809}
--
wpt-commits: 1dd0bc9ffd9b1433cb2aa1e20f972fd477c65ad4
wpt-pr: 17394
Automatic update from web-platform-tests
location.hash = '' should always result in an empty fragment, not no-fragment
So far in |setHash|, old fragment identifier and new fragment identifier are
compared ignoring nullity.
When fragment has never been set, |old_fragment_identifier| is null.
In this situation, |location.hash = ''| is called,
|new_fragment_identifier| is not null empty value.
|EqualIgnoringNullity| treats these as the same, |setHash| does nothing.
So, this patch compare old and new fragment by == operator
not |EqualIgnoringNullity|.
Bug: 615300
Change-Id: Id509bc5066eeee83236ecb4ee816ecb90540a260
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1647298
Commit-Queue: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670795}
--
wpt-commits: a3e67aed3509dc5255a029f913c5785be4e67aed
wpt-pr: 17293
Automatic update from web-platform-tests
[LayoutNG] Fix inserting exclusion crash.
When placing a new area into the closed area list there is almost
always an area at LayoutUnit::Min().
However if there was a float placed at LayoutUnit::Min() it is possible
to get into a state where this isn't the case.
Bug: 972904
Change-Id: I1c787ea8e4f5d87ae97023efd9cdb994c2b065ce
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1664930
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670726}
--
wpt-commits: 9a183439c7fd1a22298c49a86be1e293d460ea75
wpt-pr: 17391
Automatic update from web-platform-tests
SMS API: Clean up SMS API mojom interface
This CL cleans up the SMS API mojom interface based on the suggestions
on the following issue link. No behavioral changes for the SMS API
mojom interface.
Bug: 968584
Change-Id: Iba707dd9a94f75cb28b7409f930e75b0f6f2f792
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1654272
Commit-Queue: Jun Cai <juncai@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670694}
--
wpt-commits: 43ef8451989ca9be29d55ca88cb80a1ab90030a1
wpt-pr: 17304
Automatic update from web-platform-tests
[LayoutNG] Fix DCHECK(NeedsLayout) for inline oof fixed container.
NGOutOfFlowLayoutDescendant.inline_container was not being set
correctly for an Element if:
- There is an OOF containing block between Element and
its Container(). This can only happens if Element is
position:fixed.
This caused Element not to be laid out after it got dirty (but
its containing block did not).
The fix is to set inline_container when Element's
NGOutOfFlowDesecendantCandidate gets propagated up the OOF
containing block chain.
For a while, I was afraid that this fundamentally broke
the concept of inline_container. I could not come up
with a counterexample that broke this fix.
Bug: 974760
Change-Id: Id16a0057f0aefe183c30c53244dd5c46108f093c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1666809
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670634}
--
wpt-commits: b6343fc17a3035a0c2170f44fb63df2356aa2cb9
wpt-pr: 17390
Automatic update from web-platform-tests
[css-flexbox] Also skip non-flexbox items with percentages
The same percentage issue happens with regular blocks. See the
linked bug and associated testcase.
R=dgrogan@chromium.org, eae@chromium.org
Bug: 973924
Change-Id: I588353f0dcce4a446c08a8aa0f186c9ec2ee8949
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1667684
Commit-Queue: Christian Biesinger <cbiesinger@chromium.org>
Auto-Submit: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670606}
--
wpt-commits: 6515e798b30a5d3053bec1faae2f8c366fdbcba9
wpt-pr: 17396
Automatic update from web-platform-tests
[css-ui] Test serialization: `-webkit-appearance` (#17221)
* [css-ui] Test serialization: `-webkit-appearance`
* fixup! [css-ui] Test serialization: `-webkit-appearance`
Change API used to set style in order to actually test the internals
referenced by the test title.
* fixup! [css-ui] Test serialization: `-webkit-appearance`
Introduce tests for property reference
* fixup! [css-ui] Test serialization: `-webkit-appearance`
Remove duplicate assertion
* fixup! [css-ui] Test serialization: `-webkit-appearance`
Comprehensive tests for property references have been added since these
tests were written. Remove the excess assertions in order to improve the
focus of these tests.
* fixup! [css-ui] Test serialization: `-webkit-appearance`
Add equivalent tests for unprefixed `appearance` property
* fixup! [css-ui] Test serialization: `-webkit-appearance`
--
wpt-commits: 79787d6d6eff255fbe6efdbe386e92363d2b6303
wpt-pr: 17221
Automatic update from web-platform-tests
Adding a test for backdrop filter plus mask
This tests a backdrop filter element that also contains a (non-border
rect) mask or clip. It currently fails.
Bug: 974857
Change-Id: Ied65cc96deb2d02634b62d8743bff02588c94411
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662499
Commit-Queue: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670587}
--
wpt-commits: 1ace0eaddd369c7063e0a34ac91a2f361020b5bf
wpt-pr: 17366
Automatic update from web-platform-tests
Return show promise instead of the resolved value of show promise (#17389)
--
wpt-commits: e0cfe65d6e5338f501dfe0494e6ce2cc666ee978
wpt-pr: 17389
Automatic update from web-platform-tests
Worker: Add service worker interception tests for shared workers
One test case for shared workers is failing because it's not allowed to create a
dedicated worker on a shared worker.
Bug: n/a
Change-Id: I4f7139adacdccb0f16d7afedd7eaab065c4bea2c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1657855
Commit-Queue: Hiroki Nakagawa <nhiroki@chromium.org>
Reviewed-by: Matt Falkenhagen <falken@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669615}
--
wpt-commits: 3671eb9b321c60898a79c76d20a97807925ebe1e
wpt-pr: 17333
Automatic update from web-platform-tests
Initial implementation of std-toast
Intent to Implement: https://groups.google.com/a/chromium.org/forum/?utm_source=digest&utm_medium=email#!topic/blink-dev/Gl7FIKM5IFw
BUG=972945
Follow-ups will align with std-switch in elements and de-duplicate the .eslintrc.js files between toast and kv-storage.
Change-Id: Ib5837ccf8c9ea03fd2f1f2bd581e443a2936f693
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1635867
Commit-Queue: Jack Steinberg <jacksteinberg@chromium.org>
Commit-Queue: Fergal Daly <fergal@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670383}
--
wpt-commits: 17de974a80b0d9a6ff48dc24796441057afad5a0
wpt-pr: 17146
Automatic update from web-platform-tests
Removing initial Element Timing implicit registration heuristic.
The Element Timing specification originally included a provision for reporting
timings of elements that were automatically detected as 'important'. This would
allow useful information from the Element Timing API to be reported through the
Performance Timeline even if site authors neglected to mark their important
elements with the 'elementtiming' attribute.
The automatic detection of 'important' elements is, necessarily, a heuristic
and, until consensus for the correct heuristic had been reached, we were
treating any image that occupied greater than %15 of the viewport as
'automatically important'. As the Element Timing specification is still being
refined, the exact threshold and heuristic is still being investigated. Until
agreement on an appropriate heuristic is reached, implicit registration will be
disabled.
This CL removes our %15 threshold and disables implicit registration. There was
also WPT coverage to test that all browsers would respect the %15 threshold so
that test is being removed too.
Change-Id: I14847533402f5a68bb3de63a8f9acbd004c5a8e4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1643379
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Tom McKee <tommckee@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670319}
--
wpt-commits: f76b2e5e2b1dd5d73cf2351c57a303d4a67eb729
wpt-pr: 17176
Automatic update from web-platform-tests
[html] Add test for history traversal (#16478)
* [html] Add test for history traversal
* fixup! [html] Add test for history traversal
* fixup! [html] Add test for history traversal
--
wpt-commits: 7d8eefc2e4793df438d1f120737078c0bb67979e
wpt-pr: 16478
Automatic update from web-platform-tests
[IndexedDB] Promote test isolation (#16436)
* [IndexedDB] Promote test isolation
Use distinct database names for each test so that failure to clean up
from one test does not influence the result of another.
* fixup! [IndexedDB] Promote test isolation
--
wpt-commits: 23776c16a2db7b8df7374ec7c1e97a0cec003280
wpt-pr: 16436
Automatic update from web-platform-tests
[cookie-store] Promote stability in test results (#16415)
* [cookie-store] Promote stability in test results
Allow service worker activation to proceed in the absence of the API
under test. This prevents the workers in failing implementations from
entering the "redundant" state, which can interfere with the harness's
ability to detect all tests.
* fixup! [cookie-store] Promote stability in test results
* fixup! [cookie-store] Promote stability in test results
--
wpt-commits: 199b5fa5c003e348490000bc8147e0f2bb3fbaf0
wpt-pr: 16415
Automatic update from web-platform-tests
[csp] Wait for all tests to be defined (#15631)
Configure the test harness to delay completion until all
asynchronously-defined tests are available.
--
wpt-commits: 159c7c2f98576d2288c12aee86264356cbaa1be1
wpt-pr: 15631
Automatic update from web-platform-tests
Prevent leaking Sec-CH-/Sec-Fetch- Request Headers on HTTPS Downgrade Redirects.
Currently various Sec-CH- and Sec-Fetch- request headers are added through the codebase and correctly check if the request target url is trustworthy. If the destination is not trustworthy then the headers are not added. However in the event a request redirects from a trustworthy to non-trustworthy destination, such as https => http, there may be pre-existing headers present. Since these headers would not have been added to the non-trustworthy request we need to remove these extra headers from the request.
This change adds a helper call to the UrlLoader class in the network service to remove any request headers prefixed with "sec-ch-" or "sec-fetch-" when a downgrade redirect is detected. In addition to this unit test cases for the helper and end to end WPT cases have been added to validate the scenario and prevent future regressions.
Bug: 964053
Change-Id: I109c3ec1b3a05f6341c3c4adbd1a8da1274fd0d6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1647354
Commit-Queue: Brandon Maslen <brandm@microsoft.com>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#667415}
--
wpt-commits: 376e2a8250c3824b794ec518ab320d8a82cedf95
wpt-pr: 17200
Automatic update from web-platform-tests
[LayoutNG] Skip "replaced % resolution" quirk on ortho-roots.
This is about an undocumented quirk. I raised
https://github.com/whatwg/quirks/issues/46 for it.
LayoutNG currently cannot handle this situation, because we don't store
the inline-size to use in replaced percentage resolution (only the
block-size). However, I find it hard to believe that there'd be any
specific expectations to how this is supposed to work if a table cell
has a definite block-size, and a descendant establishes an orthogonal
writing-mode root. So just ignore it and use regular percentage size
resolution in these cases.
Bug: 967069
Change-Id: Iac61abe80f4f949017cc161855b2223ec4503812
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1664075
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670126}
--
wpt-commits: 361912dbe4ef692ea256b6f5bc0d74c0668ccdf5
wpt-pr: 17381
Automatic update from web-platform-tests
Integrating ScrollTimeline with main thread WebAnimations.
Changes made:
- ScrollTimeline interface is enabled under its own ScrollTimeline flag.
- Animation class now has member variable timeline_ of type AnimationTimeline instead of
DocumentTimeline.
- Document and scroll linked animations are now attached to their document global document
timeline. TODO: reconsider this approach.
Bug: 916117
Change-Id: I5f0c3d22fdb0c9b9763f5a2400c2e3d5af32e896
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1597286
Commit-Queue: Olga Gerchikov <gerchiko@microsoft.com>
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Reviewed-by: Andrey Kosyakov <caseq@chromium.org>
Reviewed-by: Stephen McGruer <smcgruer@chromium.org>
Reviewed-by: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670086}
--
wpt-commits: 31373e2726073d95b05e09ed112efac950b562b5
wpt-pr: 16755
Automatic update from web-platform-tests
CSP handling of 'self' inside sandbox iframe was incorrect.
The correct handling of 'self' depended on the timing of when the
ExecutionContext's sandbox flags were applied. If a CSP policy for 'self'
was applied after the origin was derived to be opaque it would fail.
BUG=973991
Change-Id: Ie6f384b02aa3dea3ce48c3052f06b7bd8fb2d3ea
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1658764
Commit-Queue: Dave Tapuska <dtapuska@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670074}
--
wpt-commits: b50766de4c9059ed41559315e0f12d602c8c9d59
wpt-pr: 17326
Automatic update from web-platform-tests
[Azure Pipelines] Use more verbose TBPL logging for full runs (#17379)
This is to help diagnose problems if they occur, such as this failure
to run all of the tests:
https://github.com/web-platform-tests/wpt/pull/17219#issuecomment-501272482
--
wpt-commits: 3857b199e7ee7867550b268df05664e2ef055600
wpt-pr: 17379
Automatic update from web-platform-tests
Add CEReactions and CustomElementCallbacks to toggleAttribute
Previously the IDL definition for toggleAttribute doesn't have
those modifiers, so they behave differently than setAttribute when
called on custom elements (it won't fire attributeChangedCallback, etc)
Bug: 976177
Change-Id: I7d8107db8d07a2e2ec856305c56a178339c5e05c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1663881
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Auto-Submit: Rakina Zata Amni <rakina@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670060}
--
wpt-commits: f6881fbb28940a254944e62b994b282b176bb030
wpt-pr: 17377
Automatic update from web-platform-tests
[LayoutNG] Fix NeedsLayout failure when CR/FF is dirty
This patch fixes |ClearNeedsLayout| for CR (U+000D) and FF
(U+000C). These were overlooked when |ClearNeedsLayout| was
moved from |NGInlineItemsBuilder| to |NGLineBreaker| and
|NGInlineLayoutAlgorithm|.
Bug: 971811
Change-Id: Ie3d9d3d11e35a7ed3458bb8b96d2fa68bf9c37a9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1663478
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#670010}
--
wpt-commits: 95372aa3ca35565b56fc6d9d5e0653a4fff8a6e8
wpt-pr: 17373
Automatic update from web-platform-tests
[LayoutNG] Fix DCHECK failure for table cell width quirk
This patch fixes a DCHECK failure when table cell width
calculation quirk logic[1] found an out-of-flow image.
The logic was in |BreakLine| because it may need to change
|can_break_after| of the last item. By calling
|HandleAtomicInline| in trailing item phase, the logic can
be moved to |HandleAtomicInline|.
With this change, |HandleAtomicInline| may choose to break
before the item, similar to |HandleText|.
[1] https://quirks.spec.whatwg.org/#the-table-cell-width-calculation-quirk
Bug: 968317
Change-Id: Ib4a71ca62107d2601449ba589bb2771b378ab38b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1660296
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669968}
--
wpt-commits: 2b29767a9f53e3a7a142b6c4cf72407dfe88506d
wpt-pr: 17357
Automatic update from web-platform-tests
[LayoutNG] Fix "body fills html" quirks.
We had a few issues related to quirky body elements. We were
stretching the body when it was OOF-positioned, float, or an atomic
inline when we weren't supposed to.
Bug: 967215
Change-Id: I640b1a2f6c2ab30d071e04c245a34dd1e30b19fd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1662839
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Reviewed-by: Aleks Totic <atotic@chromium.org>
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#669954}
--
wpt-commits: 90c18764adad351a28069adbfade18d6dd4949e7
wpt-pr: 17367
Automatic update from web-platform-tests
[docs] Build (but do not deploy) for pull requests
Although the documentation website should not be rebuilt in response to
pull requests, refusing to simply build the site may potentially hide
errors during the review process.
Update the documentation generation script to build the site as part of
the pull request, provided a relevant file has been modified. With this
applied, if the patch under review regresses the script, the contributor
and reviewers are immediately notified.
--
wpt-commits: 4be1e7e7b78712303076819ef8a6b3f055ebbb3c
wpt-pr: 17365
Wanming Lin
Hiroki Nakagawa
Jack Steinberg
jugglinmike
Nicolás Peña Moreno
Anders Hartvoll Ruud
Adam Rice
Dave Tapuska
Robert Ma
Dominic Farolino
Jihwan Marc Kim
Ella Ge
Ian Kilpatrick
moz-wptsync-bot
Jun Cai
Aleks Totic
Christian Biesinger
Luke Bjerring
Mason Freed
Lan Wei
Danyao Wang
Daniel Vogelheim
Tom McKee
Brandon Maslen
Morten Stenshorne
Olga Gerchikov
Philip Jägenstedt
Rakina Zata Amni
Koji Ishii
autofoolip
Kouhei Ueno