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
Automatic update from web-platform-tests[css-properties-values-api] Support comma-separated lists.
This adds support for syntax strings like "<length>#".
R=chrishtr@chromium.org
Bug: 859509
Change-Id: Ifd1ec986e5e11e8d00dfa5956f174616be857512
Reviewed-on: https://chromium-review.googlesource.com/1122625
Commit-Queue: Anders Ruud <andruud@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573293}
--
wpt-commits: 4497a88542cd6e6e0dfd14742ebc0225bbae6fb3
wpt-pr: 11756
Automatic update from web-platform-testsReplace/remove kristijanburnik in some META.yml files (#11853)
No longer active on GitHub.
--
wpt-commits: 97690698b35d56e57449c407b6b5f45a6c3487f3
wpt-pr: 11853
Automatic update from web-platform-testsUn-deprecated 'child-src'
'child-src' is now part of the fallback chain for 'worker-src'.
This means that 'child-src' always takes precedence over 'script-src'
when checking worker requests.
Added extra tests to ensure that a worker request blocked by
'child-src' and allowed by 'script-src' is blocked.
Removed previous logic that considered 'script-src' to be the
fallback for 'worker-src' and amended tests. Removed "temporary"
logic put in place to not break sites using "child-src".
Refactored the OperativeDirective logic to ensure that the caller
does not need to be aware of precise fallback chain of the directive,
otherwise the way to get the 'worker-src' operative directive would be:
OperativeDirective(worker_src_.Get(),
OperativeDirective(child_src_.Get(),
OperativeDirective(script_src_.Get())));
To be submitted with the spec PR as it includes tests.
Spec: https://github.com/w3c/webappsec-csp/pull/313
Bug: 669496
Change-Id: I7ca9552df1d0ce203a604b0e469a268f6b112e49
Reviewed-on: https://chromium-review.googlesource.com/1128087
Commit-Queue: Andy Paicu <andypaicu@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#573278}
--
wpt-commits: dceb242f223cae966354d8d4558492b28f9238cf
wpt-pr: 11838
Automatic update from web-platform-testsAdd referrer policy support to script fetching
This adds referrer policy attribute to top-level script
elements and ensures that the referrer policy for a script
specified by its attribute gets inherited by imported script
subresources.
Intent to Ship: https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/jfd4knvCiioR=hiroshige@chromium.org, kouhei@chromium.org, mkwst@chromium.org, yhirano@chromium.org
Bug: 841673
Cq-Include-Trybots: master.tryserver.blink:linux_trusty_blink_rel;master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2
Change-Id: I49650d593ba433a53793c846afc18be83dc9fc87
--
wpt-commits: 172489943de49dde6b3aa9d5d5ce5e6cc3cbd6e9
wpt-pr: 11085
Automatic update from web-platform-testssensors: Stop passing undefined as an invalid SensorOptions value (#11823)
While the undefined -> double conversion in WebIDL should indeed throw a
TypeError, we cannot forget we have a WebIDL dictionary (SensorOptions) in
the middle:
{frequency: undefined}
is essentially equivalent to
{}
so we do not actually throw a TypeError in this case at all.
--
wpt-commits: 4713ec6523e637619ec607e7882fd1e7ba54cde9
wpt-pr: 11823
Automatic update from web-platform-testsMerge pull request #10746 from bocoup/webrtc-media
[webrtc] Use procedurally-generated media streams
--
wpt-commits: eee513ca541588299fafa71a9337eceae6b680cf
wpt-pr: 10746
Bump the version number to 3.8, incorporating the LSAN changes. This
minor version bump assumes that mozlog consumers are supposed to
handle unknown actions gracefully (i.e. by ignoring them) and
therefore adding actions doesn't count as a compat-breaking change.
MozReview-Commit-ID: ECsDTuUgkfQ
Summary:
This fixes a couple fuzz bugs and prevents special-casing <svg:use> even more in
bug 1431255.
Unfortunately not as many hacks went away as I'd have hoped, since we still need
to match document rules, see the linked SVGWG issues.
But blocks_ancestor_combinators goes away, which is nice since it's on a very
hot path.
Test Plan: WPT for style invalidation, covered by existing tests otherwise.
Reviewers: heycam
Tags: #secure-revision
Bug #: 1450250
Differential Revision: https://phabricator.services.mozilla.com/D2154
MozReview-Commit-ID: C4mthjoSNFh
It's used by SVGAnimationElement, and otherwise it can't find the root element
if it's under a <use> element.
It also feels like the right thing to do, and didn't break any XBL+svg tests
(though we may as well get rid of those at this point).
Differential Revision: https://phabricator.services.mozilla.com/D2195
MozReview-Commit-ID: Jx1JrTld8EL
Summary:
We've hit stack overflows while decoding, in particular for av1. This increases
the thread size for the platform decoder threads, while leaving the others at
their default values.
Reviewers: jya
Tags: #secure-revision
Bug #: 1474684
Differential Revision: https://phabricator.services.mozilla.com/D2226
--HG--
extra : rebase_source : d03a91e93910fac5458f18f43398d76b736bbee6
Marcos Cáceres
Josh Matthews
Philip Jägenstedt
moz-wptsync-bot
Luke Bjerring
Luke Bjerring
Antoine Quint
Mark Nottingham
Majid Valipour
Nicolas Pena
Anders Hartvoll Ruud
Andy Paicu
Dominic Farolino
Raphael Kubo da Costa
Eric Willigers
L. David Baron
Soares Chen
James Graham
Emilio Cobos Álvarez
Andrea Marchesini
Dan Minor
Benjamin Bouvier
Trisha Gupta
Andreea Pavel
Tiberius Oros
Christoph Kerschbaumer
Sebastian Hengst
Tooru Fujisawa