Automatic update from web-platform-testsTests for PaymentCurrencyAmount's currencySystem (#9728)
This test is to prove that no one supports this feature - thus can be dropped from the spec.
Related issues:
* https://github.com/w3c/payment-request/issues/686
* https://github.com/w3c/payment-request/issues/617
wpt-commits: 866783a3fffaa8bdd3c29e4aec3b2f2626797c93
wpt-pr: 9728
wpt-commits: 866783a3fffaa8bdd3c29e4aec3b2f2626797c93
wpt-pr: 9728
Automatic update from web-platform-tests[css-typed-om] Whitelist supported properties.
This patch whitelists all our supported properties. Any property that
is not supported will return a base CSSStyleValue. This ensures that
we don't accidentally produce unexpected results for properties that
we haven't tested it.
We also add a few new properties to support, bringing the total number
of property tests to 50. We also remove support for 'z-index' because
it uses <integers> which we don't support yet.
transition-duration is failing tests because we currently convert
ms to seconds when we compute, which is incorrect.
Some paint/layout tests depend on properties that are not whitelisted,
so we've changed them:
- border-radius -> margin-left
- align-items -> empty-cell
Bug: 816402
Change-Id: I84d2fd8a15df92624122f0c1ecf4f7c42f928928
Reviewed-on: https://chromium-review.googlesource.com/942651
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540397}
wpt-commits: 12e0354d971ce3f705991a4f68837d24947865df
wpt-pr: 9738
wpt-commits: 12e0354d971ce3f705991a4f68837d24947865df
wpt-pr: 9738
Automatic update from web-platform-tests[css-typed-om] Fix computed value of an interpolated transform.
Previously we did not handle the case of computing the value of an
interpolated transform, which occurs when we interpolate between
two different transform types containing percentages.
The correct result is currently not spec'd [1], so this patch fixes this
by just returning "none" in this case.
[1] https://github.com/w3c/css-houdini-drafts/issues/425
Bug: 816803
Change-Id: I97c8f6b71f651a8d547fb4cb307121eba7dabdb6
Reviewed-on: https://chromium-review.googlesource.com/942595
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540258}
wpt-commits: a77669c83cc75fcec4df6e46f6a07edf8c20d1a4
wpt-pr: 9731
wpt-commits: a77669c83cc75fcec4df6e46f6a07edf8c20d1a4
wpt-pr: 9731
Automatic update from web-platform-testsbluetooth: web: test: Simulate advertisements
This change adds a SimulateAdvertisementReceived function to the
FakeCentral interface. The design for this class is detailed in the
following document:
https://docs.google.com/document/d/1XFl_4ZAgO8ddM6U53A9AfUuZeWgJnlYD5wtbXqEpzeg
BUG=719826
Change-Id: I618dc68c967e6d9942f99f1807da6fb1985cd676
Reviewed-on: https://chromium-review.googlesource.com/916554
Reviewed-by: Oliver Chang <ochang@chromium.org>
Reviewed-by: Giovanni Ortuño Urquidi <ortuno@chromium.org>
Reviewed-by: Conley Owens <cco3@chromium.org>
Commit-Queue: Ovidio Henriquez <odejesush@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540236}
wpt-commits: 5635bba261e91a9c619a789c5f482e15f60c68cb
wpt-pr: 9506
wpt-commits: 5635bba261e91a9c619a789c5f482e15f60c68cb
wpt-pr: 9506
Automatic update from web-platform-testsscrollTo and scrollBy should land on snap points.
According to spec,
https://drafts.csswg.org/css-scroll-snap-1/#scroll-types,
programmatically scrolling such as scrollTo and scrollBy should land on
snap points.
Bug: 803606
Change-Id: I1e70d88f31a2b2f93c92cc063adf653ed923adeb
Reviewed-on: https://chromium-review.googlesource.com/889936
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Sandra Sun <sunyunjia@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540166}
wpt-commits: 0f3fa6c1e32c9d6454569eb443c104ca10dd96b9
wpt-pr: 9678
wpt-commits: 0f3fa6c1e32c9d6454569eb443c104ca10dd96b9
wpt-pr: 9678
Automatic update from web-platform-testsUpdate reftest graph when node changes to support (#9732)
Modified conditional in manifest.py to check for a reftest node changing
to another type.
Wrote a test in test_manifest.py for the same
wpt-commits: 2560d71e083b5798154038589205f75f54442601
wpt-pr: 9732
wpt-commits: 2560d71e083b5798154038589205f75f54442601
wpt-pr: 9732
Automatic update from web-platform-tests[css-layout-api] Populate children, and pass into layout() function
This introduces the LayoutChild API surface, (which only has a styleMap
accessor currently).
Each LayoutBox which is a child of a LayoutCustom will hold onto a
LayoutChild object, acting as the script interface for the web
developer.
Bug: 726125
Change-Id: Iecdb01a38c0712dcda063b485c4207bde59f3995
Reviewed-on: https://chromium-review.googlesource.com/933092
Commit-Queue: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539928}
wpt-commits: 41ab079dfcde76aebbde5660fe3e417447e61f80
wpt-pr: 9680
wpt-commits: 41ab079dfcde76aebbde5660fe3e417447e61f80
wpt-pr: 9680
Automatic update from web-platform-testsMerge pull request #9716 from mrego/css-text-viewport
[css-text] Modify reference tests so they fit in the viewport
wpt-commits: 0d843d4cf1a8424884d43ead98c2528f9c6110c5
wpt-pr: 9716
wpt-commits: 0d843d4cf1a8424884d43ead98c2528f9c6110c5
wpt-pr: 9716
Automatic update from web-platform-tests[css-typed-om] Ensure properties works with css-wide keywords / var refs
There are two things that should always be supported with any property:
- css-wide keywords like 'initial'
- var refs like 'var(--A)'
This patch adds tests to ensure that this works for all the different
types of properties. Unfortunately, supporting this in shorthands
is quite difficult (we get shorthands as strings, so to reify them
we have to parse, but we can't parse in reification) so we'll leave
that for the future.
Bug: 816722
Change-Id: I1d344b73d011db81cfc3880be54823302534fd36
Reviewed-on: https://chromium-review.googlesource.com/942121
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540055}
wpt-commits: 9c3df0ea37661b7dbb9d19a7e7384c05483a2fd9
wpt-pr: 9730
wpt-commits: 9c3df0ea37661b7dbb9d19a7e7384c05483a2fd9
wpt-pr: 9730
Automatic update from web-platform-tests[css-typed-om] Implement correct ordering for StylePropertyMaps.
The correct ordering of properties depends on the type of style map:
- Computed: css properties first, then vendor prefixed ones, then
custom properties. Within each category, sort by code point.
- Inline: same order as the CSSStyleDeclaration.
- Declared: same order as the CSSRule.
Spec: https://drafts.css-houdini.org/css-typed-om-1/#stylepropertymapreadonly
Bug: 545318
Change-Id: I34fe8f0741bdcc2188926b37635672a4dda32625
Reviewed-on: https://chromium-review.googlesource.com/940381
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540066}
wpt-commits: 66ffd921b533a3da766797aad016820ee90ca465
wpt-pr: 9729
wpt-commits: 66ffd921b533a3da766797aad016820ee90ca465
wpt-pr: 9729
Automatic update from web-platform-testsMake clipboard events composed.
This corresponds to the upstream spec change on
https://github.com/w3c/clipboard-apis/pull/62
Note that synthetic events are not affected by the change.
To generate copy/cut/paste events, document.execCommand() is
used for Blink, but cannot be used for web platform tests.
Bug: 802009
Change-Id: I00df77269708458b9a6820323a1f511b7c75e513
Reviewed-on: https://chromium-review.googlesource.com/923671
Reviewed-by: Hayato Ito <hayato@chromium.org>
Reviewed-by: Gary Kacmarcik <garykac@chromium.org>
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Takayoshi Kochi <kochi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540046}
wpt-commits: 8dbff770ac61468d23313ad7ccb00ba6e2880064
wpt-pr: 9710
wpt-commits: 8dbff770ac61468d23313ad7ccb00ba6e2880064
wpt-pr: 9710
Automatic update from web-platform-tests[css-typed-om] Implement serialization for CSSUnsupportedStyleValues.
This patch implements serialization for CSSUnsupportedStyleValue.
The spec requires that:
- CSSStyleValues that are parsed from string should serialize to the
given string.
- CSSStyleValues that are obtained from CSSOM should serialize according
to [1] (although this is mostly the same as CSSOM serialization).
To implement both, we put a String on CSSStyleValue (the base class)
to store its serialization. This is only used by the subclass
CSSUnsupportedStyleValue. When we create a CSSUnsupportedStyleValue,
we set the serialization correctly depending on if it's from a string
or CSSOM. CSSUnsupportedStyleValue.toString() just outputs the stored
string.
It turns out that the string on CSSStyleValue can completely replace
its CSSValue. Instead of wrapping a CSSValue, which is fragile when
passed around arbitrarily, we simply parse the stored string whenever
we need to convert to a CSSValue. This actually was the original
design, but we changed it because we thought styleMap.set cannot
invoke parsing. Since we resolved to not expose styleMap.set to
worklets, we are allowed to parse and this is a much more robust
solution.
Serialization for shorthands requires different logic depending on
if it's a computed shorthand or a specified shorthand. This meant
that we had to create a new method for getting the serialization
and override it for different property maps.
We don't need CSSUnsupportedShorthandValue anymore, since we can
can just use CSSUnsupportedStyleValue.
[1] https://drafts.css-houdini.org/css-typed-om-1/#cssom-serialization
Bug: 816722
Change-Id: Ia236f72467e414a2eb380f00ddb196db06f8d8b6
Reviewed-on: https://chromium-review.googlesource.com/940283
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#540039}
wpt-commits: a78e2a33854504792ed5692084f8d8afc45c5585
wpt-pr: 9720
wpt-commits: a78e2a33854504792ed5692084f8d8afc45c5585
wpt-pr: 9720
Automatic update from web-platform-testsSupport wpt run safari (Safari 11 and Technology Preview) (#8979)
Based on unfinished support for Safari 10:
https://github.com/w3c/wptrunner/pull/225
Tested with Safari 11 and Technology Preview, but whether this still
works with Safari 10 has not been tested. It probably doesn't work.
Also improve the debug logging around WebDriver start and document the
manual setup required to make `wpt run safari` work.
wpt-commits: 10d9c8de236f1a332dfdd54d04496c272406a3d1
wpt-pr: 8979
wpt-commits: 10d9c8de236f1a332dfdd54d04496c272406a3d1
wpt-pr: 8979
Automatic update from web-platform-tests[css-typed-om] Implement shorthands for StylePropertyMap.set/delete.
This patch implements shorthands for stylemap.set/delete. When we
receive an UnsupportedShorthandProperty, we should get the CSSValues
out of them and set them on the style map.
We leave parsing of shorthand values for a future patch.
Bug: 816722
Change-Id: Iebd0b33f89b1d8872bea5d3f80d1dde71d72bc45
Reviewed-on: https://chromium-review.googlesource.com/938684
Commit-Queue: Darren Shen <shend@chromium.org>
Reviewed-by: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539992}
wpt-commits: d2058869b7fcb86a0ed4bfa9c4cb00a07ec3dc4c
wpt-pr: 9682
wpt-commits: d2058869b7fcb86a0ed4bfa9c4cb00a07ec3dc4c
wpt-pr: 9682
Automatic update from web-platform-testsEnable separating the metadata and manifest paths.
The current wptrunner setup assumes that the MANIFEST.json file is
always at the root of the metadata path. But there are scenarios in
which this need not be true e.g. if the metadata is in-tree and the
manifest is not. So we separate these out by porviding an extra
command line argument for the manifest path, and corresponding key in
the config file. If this is not supplied the old value is assumed as a
default.
--
Allow supplying extra properties to use when updating metadata.
The properties are read from a run_info.json and may be used to
distinguish runs. Default properties are set on a per-product
basis, but in some scenarios we want additional properties to be
considered for the metadata e.g. when updaating multi-browser metadata
we want to consider the full product name.
It may be better in the long run to simply allow overriding the full
list of properties and always having the user (or context-specific
caller) supply this list rather than having any hardcoded defaults.
--
Add a wpt command for updating expectation metadata.
The |wpt update-expectations| command takes a list of raw log files,
and updates the expectation data located in the directory supplied
thorugh the --metadata keyword argument. This metadata is used by
subsequent test runs to determine the expected test results.
By default the "product" property is used as a possible conditional on
the data; this means that if multiple logs are passed in
simultaneously then different results will be distinguished by "if
product==foo" conditions in the metadata.
--
Add a wptrunner_infrastructure job to CI.
This runs all the tests under infrastructure/ every time that the
tools/ directory changes, as a smoketest to ensure that nothing is
badly broken.
--
Add metadata for infrastructure tests
wpt-commits: 952022a07f809f917912bbc552d77ac5b9062e49, 1a17d9f7a6bb849aaa6cdf4ad8499074945d7da4, dbde4106fd461486f2e4ae2c84dcf644e854a6af, e542c4abf945a612e726a80d5efc46d98b0e59f2, b73c5d44e35f6510e200aad2242b2f4e70c607c1
wpt-pr: 9676
wpt-commits: 952022a07f809f917912bbc552d77ac5b9062e49, 1a17d9f7a6bb849aaa6cdf4ad8499074945d7da4, dbde4106fd461486f2e4ae2c84dcf644e854a6af, e542c4abf945a612e726a80d5efc46d98b0e59f2, b73c5d44e35f6510e200aad2242b2f4e70c607c1
wpt-pr: 9676
Automatic update from web-platform-tests[css-tables] Test that tables have box-sizing:border-box by default
Legacy layout erroneously sets box-sizing:border-box on non-table
elements that have display:table when the element has a specified %
height. Only <table> elements should have box-sizing:border-box.
Bug: 598134
Change-Id: I66a4a6380ca60a88516a63d3df84faabd709d4c0
Reviewed-on: https://chromium-review.googlesource.com/940561
Commit-Queue: David Grogan <dgrogan@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539916}
wpt-commits: 508c74e4cfeff84d005166adeb80f89237a70b71
wpt-pr: 9699
wpt-commits: 508c74e4cfeff84d005166adeb80f89237a70b71
wpt-pr: 9699
Automatic update from web-platform-tests[Code Health] Fix ABC wpt.browser.Browser
* Make sure methods in subclasses have the same interface as the
abstract methods in the base class.
* Move docstrings to the base class.
* Declare two more abstract methods: find_binary & find_webdriver,
because multiple (though not all) subclasses already defined these
methods, and the two methods are called externally (by wpt.run). They
fall into the same category as version().
wpt-commits: 3370b65896f68174e3092b7fbcc46aba98c47544
wpt-pr: 9349
wpt-commits: 3370b65896f68174e3092b7fbcc46aba98c47544
wpt-pr: 9349
Automatic update from web-platform-testsReporting: Use new format for Report-To header
The format of the Report-To header recently changed so that endpoint
groups are the top-level element, instead of individual endpoints.
Bug: 704259
Change-Id: I7534c46abbbb86c367931ffc060972ac36b1084b
Reviewed-on: https://chromium-review.googlesource.com/914687
Commit-Queue: Douglas Creager <dcreager@google.com>
Reviewed-by: Robert Kaplow <rkaplow@chromium.org>
Reviewed-by: Julia Tuttle <juliatuttle@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539876}
wpt-commits: fe9700afafd37617d877b36f0657cc3d9c666af0
wpt-pr: 9714
wpt-commits: fe9700afafd37617d877b36f0657cc3d9c666af0
wpt-pr: 9714
Automatic update from web-platform-testsRevert "Revert "webauthn: support the appid extension.""
This reverts commit 7df8cfae4fb4949f4949d7c3ad9411fbb50b0175. Originally
it broke because r539572 landed between the trybot runs and commit and
broke it. Original commit message:
webauthn: support the appid extension.
This extension allows credentials that were registered with U2F to be
used with webauthn. See https://w3c.github.io/webauthn/#sctn-appid-extension.
The change does not include support for echoing the extension in the
CollectedClientData[1], nor does it implement
getClientExtensionResults[2]. It's fully usable without that logic and
I have several questions about that part of the spec[3] that I would
like to understand first.
I did consider avoiding having a alternative app_param value in
//device/u2f but a) the spec says that the given appid should be tried
after the first one and b) this allows sites not to have to worry about
which protocol they registered credentials with. Instead, they can just
set this extension during the transition.
[1] https://w3c.github.io/webauthn/#sec-client-data
[2] https://w3c.github.io/webauthn/#iface-pkcredential
[3] https://github.com/w3c/webauthn/issues/803
Bug: none
Change-Id: Ie68e349af9b00de4fc986bfb1516e9650c61ef0b
Reviewed-on: https://chromium-review.googlesource.com/940524
Reviewed-by: Adam Langley <agl@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539858}
wpt-commits: fa2653332d898cd75ae4c38d3aa514adca791bf5
wpt-pr: 9700
wpt-commits: fa2653332d898cd75ae4c38d3aa514adca791bf5
wpt-pr: 9700
Automatic update from web-platform-tests[MIX]: Improve Safari support. (#8015)
Safari doesn't generate events in quite the same way as Firefox and Chrome, but
those events also aren't relevant to the MIX tests. It also doesn't like an
explicit 'type=video/ogg' declaration in '<source>' elements. This patch shifts
to a timeout model to ensure that even if events aren't triggered, we still
check whether or not the resource was loaded from the server.
wpt-commits: 5cddbd4919d12781dfc46e928547132fa7402d1c
wpt-pr: 8015
wpt-commits: 5cddbd4919d12781dfc46e928547132fa7402d1c
wpt-pr: 8015
Automatic update from web-platform-testsUse the print function in some scripts.
--
Use Python3-compatible except syntax.
--
Prepare mathml/tools/utils/misc.py for python3.
wpt-commits: f1536eed16c7b743acbf9188150041f049b646b9, b762b7fa54e2e830b6e400fc5d8c369c95c53e82, 911d525247327484c66ef851d6219a9ef555b0ac
wpt-pr: 8839
wpt-commits: f1536eed16c7b743acbf9188150041f049b646b9, b762b7fa54e2e830b6e400fc5d8c369c95c53e82, 911d525247327484c66ef851d6219a9ef555b0ac
wpt-pr: 8839
Automatic update from web-platform-testsEnsure testharnessreport.js is loaded as utf8
MozReview-Commit-ID: C5E7to91rFU
--
Ensure that static assets are cached.
Give them a max-age of 1 hour and ensure that the cache-control header
is also applied with the StaticHandler used in wptrunner.
wpt-commits: 0f77a132dd2682d6c79b759aaaad3315f8fa652e, fa24b4a4b454ddde0bc511b1858786da647b3d34
wpt-pr: 9393
wpt-commits: 0f77a132dd2682d6c79b759aaaad3315f8fa652e, fa24b4a4b454ddde0bc511b1858786da647b3d34
wpt-pr: 9393
Automatic update from web-platform-testsWebDriver: don't send a request body for HTTP GET requests
Due to the fact that Python's None is serializable as JSON,
the transport was always sending the string "null" as the body
for all requests which did not specify some other body. This
leads to HTTP GET requests with a non-zero Content-Length,
which is bad.
Fix this by only trying to encode the payload if the body
parameter has a non-default value. I don't think there is
a valid use case where a request payload is a top-level 'null'.
wpt-commits: c2c395d1ebc7fe9ed4d13745e700f08078893978
wpt-pr: 9465
wpt-commits: c2c395d1ebc7fe9ed4d13745e700f08078893978
wpt-pr: 9465
Automatic update from web-platform-testsRemove the "sound" property from the Notification interface
The property will be removed from the standard per the following PR:
https://github.com/whatwg/notifications/pull/127.
wpt-commits: 58777966260d8f1a6c5347bc7a531596543e6e80
wpt-pr: 9713
wpt-commits: 58777966260d8f1a6c5347bc7a531596543e6e80
wpt-pr: 9713
Automatic update from web-platform-tests[css-ui] Use "Ahem" instead of "ahem" in tests
"ahem" is causing flakiness on Windows, so this patch
just replaces "ahem" by "Ahem" on css-ui WPT tests.
BUG=724392,796733
Change-Id: I956e939790319ec956164f34af8c72f109c528ef
Reviewed-on: https://chromium-review.googlesource.com/940133
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#539797}
wpt-commits: 98f6f9bde502771ce9939d24f27ca823351adb33
wpt-pr: 9712
wpt-commits: 98f6f9bde502771ce9939d24f27ca823351adb33
wpt-pr: 9712
Automatic update from web-platform-tests[css-typed-om] Return transform components for computed transform.
ComputedStylePropertyMap should return computed values. For 'transform',
that's "as specified, but relative lengths converted to absolute" [1].
This means we need to return the individual transform components like
'translate3d'.
Currently there's no code to do this, so we have to roll our own.
[1] https://drafts.csswg.org/css-transforms-1/#propdef-transform
Bug: 816803
Change-Id: I64305512fa0d0ce32ba86ea2b14595b551ff1c8d
Reviewed-on: https://chromium-review.googlesource.com/938885
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539783}
wpt-commits: c56fcfd2726fbfaf495843bed3d1d4423ce72b7a
wpt-pr: 9685
wpt-commits: c56fcfd2726fbfaf495843bed3d1d4423ce72b7a
wpt-pr: 9685
Automatic update from web-platform-tests[css-multicol] Use "Ahem" instead of "ahem" in tests
"ahem" is causing flakiness on Windows, so this patch
just replaces "ahem" by "Ahem" on WPT tests.
BUG=724392,794136
Change-Id: I55ce2ee7ed36b2708da571f52256716e97a072cb
Reviewed-on: https://chromium-review.googlesource.com/940921
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#539780}
wpt-commits: a5e5a3d683d787be4a608d8bcd385f902c6ef2c2
wpt-pr: 9711
wpt-commits: a5e5a3d683d787be4a608d8bcd385f902c6ef2c2
wpt-pr: 9711
Automatic update from web-platform-testsgetCapabilities() should not have range properties without valid values
This CL ensures that MediaStreamTrack.getCapabilities() does not have
range properties if they don't have a valid range.
Bug: 293292
Change-Id: I6f85086fb4af7e17faca069f76299a0256f1872d
Reviewed-on: https://chromium-review.googlesource.com/938983
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539778}
wpt-commits: ca3bede481b3c4e1510e19e0c816128307ef7dcb
wpt-pr: 9688
wpt-commits: ca3bede481b3c4e1510e19e0c816128307ef7dcb
wpt-pr: 9688
Automatic update from web-platform-testsFix a bug of <fieldset disabled> detection logic.
HTMLFormControlElement::UpdateAncestorDisabledState() checked if the
highest <legend> is the first <legend> child of the highest disabled
<fieldset>. It should check <lengend> child of every disabled fieldset
ancestors.
Bug: 817181
Change-Id: I8f7dedd8089757d9eae726de359b0efe47cf9f44
Reviewed-on: https://chromium-review.googlesource.com/940644
Reviewed-by: Yoshifumi Inoue <yosin@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539776}
wpt-commits: 51071878ed91e88ba8bcf59b0180beb3dd5211a8
wpt-pr: 9709
wpt-commits: 51071878ed91e88ba8bcf59b0180beb3dd5211a8
wpt-pr: 9709
Automatic update from web-platform-tests[css-text] Use "Ahem" instead of "ahem" for fonts in tests
Using the lowercase version causes flakiness on Windows
(see crbug.com/724392).
BUG=817030
Change-Id: Ic4bdea7d40f0c2e96d6669430b3cce7a296e8d55
Reviewed-on: https://chromium-review.googlesource.com/940123
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Manuel Rego Casasnovas <rego@igalia.com>
Cr-Commit-Position: refs/heads/master@{#539748}
wpt-commits: cc52c7e80c940a475adc28142285082f2c973ed6
wpt-pr: 9707
wpt-commits: cc52c7e80c940a475adc28142285082f2c973ed6
wpt-pr: 9707
Automatic update from web-platform-testsAdd test to check that StylePropertyMap sorts in increasing code-point order
Change-Id: I86933692bff974d3a640cef4ea47b602c88e92a1
Reviewed-on: https://chromium-review.googlesource.com/940723
Reviewed-by: Darren Shen <shend@chromium.org>
Commit-Queue: nainar <nainar@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539708}
wpt-commits: 8c4cf0026a8c041c8e9efb8d0f5553a2a0eff008
wpt-pr: 9704
wpt-commits: 8c4cf0026a8c041c8e9efb8d0f5553a2a0eff008
wpt-pr: 9704
Automatic update from web-platform-tests[css-typed-om] Implement shorthands for .get/.getAll/.has.
This patch implements shorthands for stylemap.get/getAll/has. Shorthands
are implemented as a base CSSStyleValue. They are different to other
properties because they cannot be converted to a single CSSValue.
Instead, we need to store the CSSValues of their longhands so that
they can be set again on the same property.
Patches to come:
- styleMap.set/update
- Serialization of these values.
Bug: 816722
Change-Id: Ia2c3f694809c219566b965ebfae40bc38d74f4c5
Reviewed-on: https://chromium-review.googlesource.com/938881
Reviewed-by: nainar <nainar@chromium.org>
Commit-Queue: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539594}
wpt-commits: 1d8bc90c101290f6c826467ca329220a210df1ad
wpt-pr: 9681
wpt-commits: 1d8bc90c101290f6c826467ca329220a210df1ad
wpt-pr: 9681
Automatic update from web-platform-testswebauthn: support the appid extension.
This extension allows credentials that were registered with U2F to be
used with webauthn. See https://w3c.github.io/webauthn/#sctn-appid-extension.
The change does not include support for echoing the extension in the
CollectedClientData[1], nor does it implement
getClientExtensionResults[2]. It's fully usable without that logic and
I have several questions about that part of the spec[3] that I would
like to understand first.
I did consider avoiding having a alternative app_param value in
//device/u2f but a) the spec says that the given appid should be tried
after the first one and b) this allows sites not to have to worry about
which protocol they registered credentials with. Instead, they can just
set this extension during the transition.
[1] https://w3c.github.io/webauthn/#sec-client-data
[2] https://w3c.github.io/webauthn/#iface-pkcredential
[3] https://github.com/w3c/webauthn/issues/803
Bug: none
Change-Id: I22819adda99fbef9f10d38e797d08691dab7545d
Reviewed-on: https://chromium-review.googlesource.com/920659
Reviewed-by: Robert Sesek <rsesek@chromium.org>
Reviewed-by: Balazs Engedy <engedy@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Kim Paulhamus <kpaulhamus@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539584}
wpt-commits: a200a0fb41dba43d82e3810e884a838ee835aa98
wpt-pr: 9613
wpt-commits: a200a0fb41dba43d82e3810e884a838ee835aa98
wpt-pr: 9613
Automatic update from web-platform-tests[css-typed-om] remove duplicate test.
there are duplicate tests. so remove one of them.
Bug: 774887
Change-Id: I040ac68b8d2752ea7f952a0ff615f5352cb23b0e
Reviewed-on: https://chromium-review.googlesource.com/939881
Commit-Queue: Hwanseung Lee <hwanseung@chromium.org>
Reviewed-by: Darren Shen <shend@chromium.org>
Cr-Commit-Position: refs/heads/master@{#539568}
wpt-commits: bdee13ee73cbb7036363462c456355e461d5262f
wpt-pr: 9695
wpt-commits: bdee13ee73cbb7036363462c456355e461d5262f
wpt-pr: 9695
Automatic update from web-platform-testsRun script directly and don't source it
--
Fix paths when building CSS testsuite
--
Recommend `git submodule` instead of hg for w3ctestlib/apiclient
--
Fix passing arguments to ./build-css-testsuites.sh
--
Update w3ctestlib submodule
--
Update CSS build system requirements
--
Make it possible to set RUN_JOB globally
wpt-commits: e00868e2cc32b51bcc597400ef4ec1ca0fd5e4a7, 009fd7558acd69310568df2adf4292b9f10914af, 5241f45421bb3455b6b3bc362fa63293eb58ce48, fc544d570321a72c7418d45031db456db37c98be, 6b044b942db61b0f91454f254b1b1847c2d36e29, 11da4202dd2541e2dc2d36a4a3b2e265b4fcc6cc, 1305210bed8f4e3ef811998b219f220511d9a27d
wpt-pr: 9602
wpt-commits: e00868e2cc32b51bcc597400ef4ec1ca0fd5e4a7, 009fd7558acd69310568df2adf4292b9f10914af, 5241f45421bb3455b6b3bc362fa63293eb58ce48, fc544d570321a72c7418d45031db456db37c98be, 6b044b942db61b0f91454f254b1b1847c2d36e29, 11da4202dd2541e2dc2d36a4a3b2e265b4fcc6cc, 1305210bed8f4e3ef811998b219f220511d9a27d
wpt-pr: 9602
