Automatic update from web-platform-testsBring RTCCertificate interface up to date with Candidate Recommendation
--
Merge pull request #10271 from aboba/patch-1
Bring RTCCertificate interface up to date with Candidate Recommendation
--
wpt-commits: f31ef37b39dad03d8ba2fcfff0265c662c3bcd8c, 9dd2979bf76aaf62017bc7e9a12706cd64cd2227
wpt-pr: 10271
Automatic update from web-platform-testswebrtc: make a call without announcing SSRCs in the SDP
while testing receiving video still works by listening for
loadedmetadata
--
webrtc: also remove msid lines
--
Merge pull request #13526 from fippo/no-ssrcs
webrtc: make a call without announcing SSRCs in the SDP
--
wpt-commits: 23f4c21d0e21274971d1d3f98e6439fdddb756e7, 716f4c3edba97f07bb125b18ffb73d2f6bb0338b, c18f62e684c7be955b5a5b5a7906836633bea9ed
wpt-pr: 13526
Automatic update from web-platform-testsIndexedDB: fix minor nits in databases() WPTs
Fixing minor nits with IndexedDBFactory databases() WPTs as suggested
by jsbell@ over email
-assert_object_equals is deprecated and shouldn't be used. Prefer to
test the results explicitly, even though it's more code.
-all of the test cases use 1 for the version - we should have tests
for databases at other versions.
-the assertion messages should have the form ".... should be ...",
describing what is being asserted, rather than attempting to diagnose
the problem (it's easier to verify that the assertions match the spec
that way)
-there are a handful of lines missing semicolons
-the trailing done() should not be needed for .any.js tests
Bug: 899085
Change-Id: Ie8831c26fabe0e043ccba8238925ac7f520d1d69
Reviewed-on: https://chromium-review.googlesource.com/c/1313275
Reviewed-by: Daniel Murphy <dmurph@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Commit-Queue: Andreas Butler <andreasbutler@google.com>
Cr-Commit-Position: refs/heads/master@{#605128}
--
wpt-commits: 4ff6f151a21ef885d4e7a41122907862ae5ae037
wpt-pr: 13856
Automatic update from web-platform-tests[css-text] Keep track of the initial offset for each handled text
In order to identify single leading white-spaces as potential line
breaking opportunities we need to know the offset the iterator starts
at for the current text to handle.
When we landed the change in r596406 we incorrectly assumed that
leading white-spaces were always at offset 1. However, this is not
valid when such leading white-spaces are generated by previous broken
lines.
This CL solves the issue by using the stored initial offset to identify
such single leading white-spaces as potential breaking opportunities.
Bug: 900727
Change-Id: Ibc9dda7632d72ed82a61025015489ec3b70d6919
Reviewed-on: https://chromium-review.googlesource.com/c/1311274
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605055}
--
wpt-commits: c583bcd7eb30f38cb2d673031cde245776f1da5a
wpt-pr: 13830
Automatic update from web-platform-testsDon't allow popups during page unloading times.
Precisely, this disallows them when the event loop's
termination nesting level is nonzero.
This is now part of the spec,
https://html.spec.whatwg.org/#apis-for-creating-and-navigating-browsing-contexts-by-name
> The window open steps, given a string url, a string target, and a string features, are as follows:
> 1. If the event loop's termination nesting level is nonzero, return null.
BUG=844455
Change-Id: I85fb003063f5ed051049c7c263391835421902ac
Reviewed-on: https://chromium-review.googlesource.com/c/1180296
Commit-Queue: Avi Drissman <avi@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#605025}
--
wpt-commits: ffeba23ebd16b9adb2e0e2b5fe6923fef9bb9e5e
wpt-pr: 12577
Automatic update from web-platform-testsUse USB mojo interfaces in WebUsbDetector.
This CL converted USB callings in WebUsbDetector to mojo interfaces
by introducing webusb_landing_page in UsbDeviceInfo.
Bug: 699790
Change-Id: I6352c35a7eb9090ef4d5cb3d2436b30216d76ec9
Reviewed-on: https://chromium-review.googlesource.com/c/1297747
Commit-Queue: Donna Wu <donna.wu@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604923}
--
wpt-commits: 843887c17db71d57a4466599cf42f494bea6af1c
wpt-pr: 13718
Automatic update from web-platform-testsKeep previous_in_flow across shadow boundary.
For some reason we created a new AttachContext entering a ShadowRoot for
AttachLayoutTree. If the shadow host was display:contents we would lose
the previous_in_flow from the shadow tree checking the need for
whitespace LayoutObject for shadow host siblings.
Created a common space-separated words expectation for css.
Bug: 901323
Change-Id: Ib2fa54d55923c0497ff8e96c5010e68b01570881
Reviewed-on: https://chromium-review.googlesource.com/c/1314589
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604910}
--
wpt-commits: 25b7275dd46568b0ba28201940cadac3045616ff
wpt-pr: 13872
Automatic update from web-platform-testschange test order (#13861)
* change test order
Switching order of tests so these click ones can run before canMakePayment() gets upset.
* split up tests
--
wpt-commits: 96d09d3b3b8b8794063e6cd2c5bfe3dd8a4a395c
wpt-pr: 13861
Automatic update from web-platform-testsExtract Safari version from safaridriver (#13467)
--
wpt-commits: bd9dbc0d99bdadc541cd55a0309730d2bf40df1b
wpt-pr: 13467
Automatic update from web-platform-testsConsolidate the flake8 setup into tools/tox.ini and config files (#13865)
flake8 is still run as part of the "tools/ unittests (Python 2)" job in
Travis, because `run_applicable_tox` in tools/ci/ci_tools_unittest.sh
will turn `TOXENV=py27` into `TOXENV=py27,py27-flake8`.
Splitting flake8 into a separate job entirely is left for later.
--
wpt-commits: a54a387e5d474670fbe0431eb8a898df603ec0eb
wpt-pr: 13865
Automatic update from web-platform-tests[css-properties-values-api] Invalidate paint worklet on registration.
Due to how initial values of registered custom properties used to be
handled, the style diff function for custom paint could not discover that
the computed value for some property changed due to a new property
registration.
This meant that, if you used the property '--x' in your paint worklet
(without applying '--x' on any element in the document), and _then_
registered the property '--x' (giving it an initial value), the worklet
would not repaint even though the computed value of --x changed from
"nothing" to the registered initial value.
Now that initial values are returned from ::GetRegisteredVariable, simply
compare those values when diffing for custom paint invalidation.
Note that the second test in this CL is already passing before this CL,
but I'm including it anyway since that case is also mentioned in the bug.
R=ikilpatrick@chromium.org
Bug: 657706
Change-Id: I2b7707d48d73693a70b100fe1121bd7f977b4db1
Reviewed-on: https://chromium-review.googlesource.com/c/1309788
Commit-Queue: Anders Ruud <andruud@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604607}
--
wpt-commits: 2a5673603f719fed9b3dce2f6bde705057b90599
wpt-pr: 13822
Automatic update from web-platform-testsMake Element#innerText not to emit Tab/Newline for <td>/<tr>/<br> itself
This patch changes |Element#innerText| not to emit Tab/Newline for <td>, <br>,
<tr> itself to follow the spec change[1] for improving interop.
Example:
- <br>.innerText -> "" (was "\n")
- <td>abc</td>.innerText -> "abc" (was "abc\t")
- <tr><td>abc</td></tr>.innerText -> "abc" (was "abc\n")
[1] https://github.com/whatwg/html/pull/4132 Make innerText getter not run the
algorithm on the element itself
Bug: 897373
Cq-Include-Trybots: luci.chromium.try:linux_layout_tests_layout_ng
Change-Id: I4266ee28df9b44e9044dfa60c2d54257a5f82eeb
Reviewed-on: https://chromium-review.googlesource.com/c/1312436
Reviewed-by: Yoichi Osato <yoichio@chromium.org>
Commit-Queue: Yoshifumi Inoue <yosin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604872}
--
wpt-commits: ff0b6d883e558c94a2302985d424606a80ed5200
wpt-pr: 13835
Automatic update from web-platform-tests[css-text] word-break:break-all does not affect punctuation (#13415)
Turns into an proper wpt test case the test discussed in https://github.com/w3c/csswg-drafts/issues/785#issuecomment-374866706
--
wpt-commits: b61f5da2f084542d060e954209a4794f346c789a
wpt-pr: 13415
Automatic update from web-platform-tests[css-text] word-break:keep-all with U+3000 (space) and U+3001 (punctuation) (#13211)
At the time of writing, Chrome passes, but Firefox and Safari fail.
Related to https://github.com/w3c/csswg-drafts/issues/3142
--
wpt-commits: ac65f580b18722c161a59fe1a4436f17f6acda2d
wpt-pr: 13211
Automatic update from web-platform-tests[css-overscroll-behavior] Inheritance, initial (#13677)
Properties inherit or not according to the spec.
Properties have initial values according to the spec.
https://drafts.csswg.org/css-overscroll-behavior/#property-index
--
wpt-commits: 69a295238d917c2438c0029a143757a99768f275
wpt-pr: 13677
Automatic update from web-platform-testslocation.pathname should return "blank" when there is no browsing context (#13854)
The pathname of "about:blank" is "blank", not "".
--
wpt-commits: a6322a0bf9f7b0553dec4c8eee5a673fccf9a91b
wpt-pr: 13854
Automatic update from web-platform-tests[Presentation API] Remove from insecure contexts.
This patch removes the Presentation API from insecure contexts. The number of presentations started on insecure contexts is 0.0001% of page views on desktop and 0.0004 on Android.
In addition it updates layout tests and WPT to use https: for presentation URLs.
Blink-dev thread:
https://groups.google.com/a/chromium.org/d/topic/blink-dev/lumj0lVdtHA/discussion
chromestatus.com feature entry:
https://www.chromestatus.com/feature/5766218384408576
Bug: 733381
Change-Id: I9ae3025160b0e0bcf987fda0068a0e6bd92c24fd
Reviewed-on: https://chromium-review.googlesource.com/c/1306336
Reviewed-by: Mounir Lamouri <mlamouri@chromium.org>
Commit-Queue: mark a. foltz <mfoltz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604621}
--
wpt-commits: 68c63e96b88dfaceb492a8247ea8830484bf8007
wpt-pr: 13794
Automatic update from web-platform-testsFix link markup in signed-exchange/README.md (#13790)
--
wpt-commits: 088f63b9c303e1e3a5be74058c0b81a5d30502f2
wpt-pr: 13790
Automatic update from web-platform-tests[css-properties-values-api] Store initial variables on ComputedStyle.
Initial values are currently not stored at all on ComputedStyle, and we
must refer to the PropertyRegistration to figure out what the initial value
for a given property is.
The problem with this, is that registering a property also has the effect
of giving all styles that are already computed new values (effectively).
For example, if a property '--x' is not registered (and not applied on any
style), the computed value of that property is the "empty value" as
described in css-variables. If the property then becomes registered,
the initial value suddenly becomes whatever is specified by the
registration, even on the ComputedStyle objects that already exist.
This causes problems for calculating transitions, because we incorrectly
consider the previous computed value to be "initialValue" from the
registration rather than what it really was: "empty value".
This CL adds a StyleInitialData class which contains the initial values
for all registered variables. This class is instantiated for the initial
style, and then referenced by all ComputedStyles that inherit from that
style.
This makes it possible to know what the initial value was for a certain
property at the time style calculation took place.
R=futhark@chromium.org
Bug: 848250
Change-Id: I0a44e06608738aab15cb35fbc448a47188932600
Reviewed-on: https://chromium-review.googlesource.com/c/1309736
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Anders Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604580}
--
wpt-commits: bce35cc67fe84021df94dc52e60522b1f1b46e8b
wpt-pr: 13816
Automatic update from web-platform-testsAdd extra utilities to content::media_constraints
This CL adds:
* NumericRangeSet::Contains().
* NumericRangeSet::EmptySet().
* ResolutionSet::FromNativeResolution().
These utilities are in preparation for supporting the resizeMode
constrainable property in getUserMedia() and applyConstraints().
Drive-by: minor fixes/improvements.
Bug: 854980
Change-Id: I858f406308aa9bba40521d5e740219b72e2c8a48
Reviewed-on: https://chromium-review.googlesource.com/c/1308133
Reviewed-by: Henrik Boström <hbos@chromium.org>
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Cr-Commit-Position: refs/heads/master@{#604574}
--
wpt-commits: 5b699ddb3200ce3abc8a2a5059c52235076bde4f
wpt-pr: 13845
Automatic update from web-platform-tests[Azure Pipelines] Split manifest update into a separate step (#13831)
For some reason, manifest generation is faster this way.
Drive-by: don't use multi-line script where not needed
--
wpt-commits: 46e12063c39422833ea51552e86b200175be0f1a
wpt-pr: 13831
Bernard Aboba
Philipp Hancke
Andreas Butler
moz-wptsync-bot
Javier Fernandez
Avi Drissman
Robert Ma
Donna Wu
Charles Vazac
Rune Lillesveen
Philip Jägenstedt
Marcos Cáceres
Morten Stenshorne
YUHAN WU
Anders Hartvoll Ruud
Yoshifumi Inoue
Florian Rivoal
Anne van Kesteren
Dominic Farolino
Eric Willigers
Chris Dumez
mark a. foltz
Guido Urdaneta
Wanming Lin