Automatic update from web-platform-tests[css-layout-api] Don't use LayoutNG for custom layout children.
Custom layout children may not establish new formatting contexts, and
since the custom container itself is laid out by the legacy engine, we
need to force its children to be laid out by legacy as well.
Added a margin collapsing test that used to fail in NG because of this.
Change-Id: Id320f60fb76b0ed6563fb2b88f6936ac37efc1fd
Reviewed-on: https://chromium-review.googlesource.com/1131179
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573864}
--
wpt-commits: b47e2cd91cfe1b2246655b6612c407898939588c
wpt-pr: 11887
Automatic update from web-platform-testsAdd tests for (module dedicated|classic shared) worker's URLs
This CL adds WPT tests for
- WorkerLocation (wpt/workers/interfaces/WorkerGlobalScope/location/),
- referrer (wpt/xhr/), and
- API base URL (wpt/workers/baseurl/)
that should reflect worker global scope's URL, for
- classic shared workers and
- module classic workers.
Some tests are half-migrated to fetch_tests_from_worker()-style
to test shared workers easily, while the tests for
module workers uses the existing non-fetch_tests_from_worker()-style
tests, because testharness.js can't be used from module scripts.
Bug: 861564
Change-Id: I62fa415647da47e00bf7cbf4d7648f5d64377c04
Reviewed-on: https://chromium-review.googlesource.com/1128517
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Hiroki Nakagawa <nhiroki@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573840}
--
wpt-commits: 1eefa00af8eb0137b4812d0947a38fb5b76cd04e
wpt-pr: 11846
--HG--
rename : testing/web-platform/tests/workers/baseurl/alpha/sharedworker.html => testing/web-platform/tests/workers/baseurl/alpha/sharedworker-in-worker.html
rename : testing/web-platform/tests/workers/baseurl/alpha/worker.html => testing/web-platform/tests/workers/baseurl/alpha/worker-in-worker.html
Automatic update from web-platform-testsMove [SecureContext] to NavigatorBluetooth
This change moves the [SecureContext] extended attribute from the
individual attributes on the Bluetooth interface to the entire partial
Navigator interface for Web Bluetooth.
This has the practical effect of making the entire navigator.bluetooth
attribute undefined in in-secure contexts rather than only
navigator.bluetooth.requestDevice.
Web Platform Tests are also updated to test access to this attribute
from both secure and in-secure contexts.
Bug: 860798
Change-Id: Ife32dcfe9d035613c41399d7189e087cdb9f54d6
Reviewed-on: https://chromium-review.googlesource.com/1128248
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Reviewed-by: Jeffrey Yasskin <jyasskin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573780}
--
wpt-commits: 0dcad092b51b7e71890565a7df114a1955a84b78
wpt-pr: 11839
--HG--
rename : testing/web-platform/tests/bluetooth/idl/idl-NavigatorBluetooth.html => testing/web-platform/tests/bluetooth/idl/idl-NavigatorBluetooth.https.html
rename : testing/web-platform/tests/bluetooth/idl/idlharness.tentative.window.js => testing/web-platform/tests/bluetooth/idl/idlharness.tentative.https.window.js
Automatic update from web-platform-tests[testharness.js] Report error for worker errors (#11400)
Ensure that uncaught exceptions in typical worker tests cause the
harness to report an ERROR status, and update the corresponding test
accordingly. Add a test to verify that the harness reports an OK status
in response to uncaught exceptions which originate from "single-page
test" workers.
--
wpt-commits: 98848dff9fe765e3719484392fa27458f5a21c54
wpt-pr: 11400
Automatic update from web-platform-testsVerify that invalid selectors throw for empty elements
--
wpt-commits: 553778eb487e687efc08ef81b77206c7b91dd930
wpt-pr: 11848
Automatic update from web-platform-testsDisallow font-relative units when resolving var() for font-size.
For a registered custom property --foo, the following is no longer
allowed:
--foo: 10em;
font-size: var(--foo);
The same applies to ex and ch, as well as rem on the root element.
This is because --foo depends on font-size via the 'em' unit, and
font-size depends on --foo via the var() reference. This creates a
circular dependency that must be resolved somehow. The agreed-upon way
to resolve that, has been by treating the whole var() reference as
invalid.
This patch implements that cycle detection by adding flags to disallow
resolution of any var() references that contain font-relative units.
These flags are set in ResolveVariableReferences based on the
CSSPropertyID/StyleResolverState.
When a custom property itself contains var() references, it needs to
"inherit" the font-unit-ness from the resolved variables (similar to
is_animation_tainted). This is why flags have also been added to Result.
Bug: 848698
Change-Id: Ife0570949d996c5fc26dc10b1d7ca15bd27343b1
Reviewed-on: https://chromium-review.googlesource.com/1120334
Commit-Queue: Anders Ruud <andruud@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573712}
--
wpt-commits: a8bd7948236886b2dbce7456beb0406e7d2207a1
wpt-pr: 11748
Automatic update from web-platform-testsReplace/remove ayg in suggested_reviewers in META.yml (#11852)
Responsibilities distributed as discussed in
https://github.com/web-platform-tests/wpt/issues/11521.
In html/, because there aren't obvious candidates for some of the
subdirectories, instead expand html/META.yml to include all present
editors of the HTML standard.
In the past year, most of the action has been in html/semantics/, and
the busiest of the directories within do all have more granular
reviewers, so hopefully this is an improvement.
Fixes https://github.com/web-platform-tests/wpt/issues/11521.
--
wpt-commits: d332f12c8af648643c54082194c120ba654100a2
wpt-pr: 11852
Automatic update from web-platform-testsRemove .gitkeep files in 2dcontext/ and html/ (#11851)
These were added in commit 818bcab4ba58d2bc8dba94276c8b944c76570a19
and reflect the structure of the HTML spec as it was in 2012.
The structure largely remains the same, but some directories like
webappapis/user-prompts/dialogs-implemented-using-separate-documents/
are gone from the spec (https://github.com/whatwg/html/pull/374) and
others like introduction/ are non-normative and should never be
populated.
But mainly, a lot of empty directories is a nuisance when exploring
the directory in a file manager or on GitHub.
The number of directories in 2dcontext/ and html/ combined decreases
by almost 200, from 653 to 456.
--
wpt-commits: ddfe9c089bab565a9d3aa37bdef63d8012c1a94c
wpt-pr: 11851
Automatic update from web-platform-testsMerge pull request #11880 from graouts/overlapping-keyframes
Don't assume opacity computed values are exactly the same as specified on keyframe input
--
wpt-commits: afc3a452f2020dc10c51f467a435ba5b32dc0589
wpt-pr: 11880
Automatic update from web-platform-testsUpdate the generic-sensor IDL test (#11824)
--
wpt-commits: 66218ca7d67e968f2e1384d6bba97e4c47a08061
wpt-pr: 11824
Automatic update from web-platform-tests[web-animation] Make contain/will-change/writing modes props not animatable
Match the recent CSSWG resolutions:
https://github.com/w3c/csswg-drafts/issues/2737#issuecomment-402574750https://github.com/w3c/csswg-drafts/issues/2751#issuecomment-402604609
Make following properties none animatable:
* contain
* direction
* display
* text-orientation
* unicode-bidi
* will-change
* writing-mode
Note that wpt tests have already been updated for direction and writing-mode
here [1]
[1] 41f4ab65b2
Bug: 860359
Change-Id: I3e7296e3c28ff494eddbc6f011621dd29ba7d2aa
Reviewed-on: https://chromium-review.googlesource.com/1127062
Commit-Queue: Majid Valipour <majidvp@chromium.org>
Reviewed-by: Eric Willigers <ericwilligers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573509}
--
wpt-commits: 7f017e863fec0f00ab1eb531b1bc12864d850d06
wpt-pr: 11813
Automatic update from web-platform-testsUse AtomicString for PerformanceEntry::entryType()
This CL makes PerformanceEntry::entryType() a pure virtual method
instead of storing |entry_type_|. It also changes the usage from String
to AtomicString. Only PerformanceEventTiming keeps |entry_type_| since
it can be 'event' or 'firstInput'.
Since the entry type is no longer available from the PerformanceEntry
constructor, we change EntryTypeEnum() to pure virtual too.
Bug: 852050
Change-Id: Ie02040b52cf17c7563667ef440bbb78ae97e64c7
Reviewed-on: https://chromium-review.googlesource.com/1113671
Commit-Queue: Nicolás Peña Moreno <npm@chromium.org>
Reviewed-by: Yoav Weiss <yoav@yoav.ws>
Reviewed-by: Timothy Dresser <tdresser@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573442}
--
wpt-commits: d59ad168b7820ace3bfc7c80707f9d1b08a6f313
wpt-pr: 11773
Automatic update from web-platform-tests[testing] Remove per platform expectations for wpt animation-types tests
The only difference that required per platform expectation files was
the fact that 'hyphens: auto' is only supported in Chromium on Mac.
These tests don't care about the actual css property value but how one
value is animated to another in web animation interpolation model. So instead of
using 'auto' for hyphens, we use 'none' which is supported on all platforms.
This help remove three 500+ lines per platform expectation files and reduce
unnecessary maintenance burden.
Change-Id: I5f3b716ce11a72a5235e7899d2e90f4bbea77ebc
Bug: 860359
Reviewed-on: https://chromium-review.googlesource.com/1129201
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Majid Valipour <majidvp@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573328}
--
wpt-commits: 028ff8d15432d595df85c2becf66cce686659de7
wpt-pr: 11860
Andreas Tolfsen
James Graham
Tokio Kajitsuka
sotaro
Emilio Cobos Álvarez
Jason Laster
Marco Castelluccio
moz-wptsync-bot
Luke Bjerring
Morten Stenshorne
Hiroshige Hayashizaki
Reilly Grant
Simon Pieters
Zirro
Anders Hartvoll Ruud
Marcos Cáceres
Josh Matthews
Philip Jägenstedt
Luke Bjerring
Antoine Quint
Mark Nottingham
Majid Valipour
Nicolas Pena