I couldn't come up with a way to effectively cause this effect with
regular CSS I could put in marquee.css... But this matches the legacy
xul behavior and the chrome behavior, which should be compatible.
This undoes a reftest expectation change I included in bug 1618584. Our
behavior in those tests before this patch matches Safari, but Safari
passes the test I'm adding on this bug, so it is somewhat inconsistent.
Differential Revision: https://phabricator.services.mozilla.com/D105045
Automatic update from web-platform-tests
Revert "[TablesNG] Implement column track merging"
This reverts commit 2dadda0cccbda46a2fffe23e8c607e88f4d45394.
Reason for revert: Suspected cause of paint/tables/huge-table-composited-scroll-collapsed-borders.html failures
https://ci.chromium.org/ui/p/chromium/builders/ci/WebKit%20Linux%20ASAN/22054
Original change's description:
> [TablesNG] Implement column track merging
>
> One the a11y requirements was that tables should do track merging.
> I've skipped implementing this initially because there was major
> disagreement about what to do.
>
> This implementation follows the standard.
> Columns defined by TD or COL are merged for table-layout:auto,
> and not merged for table-layout:fixed.
>
> Legacy did not follow the standard for columns defined by TDs:
> they were always merged. Firefox implementation was closer to
> standard, but sometimes buggy.
>
> This changes results of some tests. Almost all of them are because
> "TablesNG is more standards compliant", and new renderings match
> FF.
>
> There is disagreement about treatment of empty rows between
> FF and TablesNGNG.
>
> external/wpt/css/css-tables/html5-table-formatting-1.html
> external/wpt/css/css-tables/html5-table-formatting-2.html
>
> The rest of the changes render better, just like FF.
>
> Two new tests have been added:
> wpt/css/css-tables/column-track-merging.html
> tests the standard.
>
> accessibility/table-column-track-merging.html
> tests Chrome's a11y API.
>
> Change-Id: Ia222351f7c500963ace556d76c26fcefb1df24e1
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2670193
> Commit-Queue: Aleks Totic <atotic@chromium.org>
> Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
> Reviewed-by: David Grogan <dgrogan@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#852958}
TBR=dgrogan@chromium.org,ikilpatrick@chromium.org,atotic@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com
Change-Id: Id914684949be4eb6196a850bb1168d25872346ef
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2690334
Reviewed-by: Thiemo Nagel <tnagel@chromium.org>
Commit-Queue: Thiemo Nagel <tnagel@chromium.org>
Cr-Commit-Position: refs/heads/master@{#853075}
--
wpt-commits: 496c290543d0572ec532b092a3b2e7fe03381293
wpt-pr: 27590
Automatic update from web-platform-tests
Include print reftests in the `./wpt tests-affected` logic
--
wpt-commits: 35c43e0c51326c7f60a2623362720b46783675c0
wpt-pr: 27582
Automatic update from web-platform-tests
Check MIME type against asserted module type in ModuleScriptFetcher
Add module type to the module map key.
Plumb module type into ModuleScriptFetcher and its subclasses, and
require that the MIME type match the type that was specified with
import assertions.
Add the necessary import assertions to the JSON/CSS module web tests
so that they continue passing. Add tests to ensure that the modules
don't load when the correct assertion is not present.
A minor functional change to JSON modules is that trying to start a
a Worker with a top-level JSON module (e.g. new Worker("./foo.json"))
now results in a rejected Promise, instead of loading a no-op worker
without an error. This change follows the spec change at
https://github.com/whatwg/html/pull/5658/; note that the invocation
of 'fetch a single module script' from 'fetch a worklet/module worker
script graph' doesn't pass a ModuleRequest, so the type is assumed to
be JavaScript, and a failure will be triggered if the MIME type is
not JavaScript.
Some of the non-virtual versions of the tests now time out because
the import assertion syntax is seen as a syntax error when
--harmony-import-assertions is not enabled, causing <script>s not to
run. TestExpectations is updated to account for these.
Bug: 1132413
Change-Id: I01bf7d907a96e791208534c9c4f2af11434c76db
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2674259
Commit-Queue: Dan Clark <daniec@microsoft.com>
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852991}
--
wpt-commits: 2c6f296858c62d4628bf58d2db4af687edbf674e
wpt-pr: 27497
Automatic update from web-platform-tests
webcodecs: Audio encoding and decoding full cycle test
Plus minor improvement in debugging logs.
Bug: 1094182, 1177021
Change-Id: I8f0b6991b645cf1262fdd135478a9a73d7cd5b39
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2688624
Commit-Queue: Eugene Zemtsov <eugene@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852980}
--
wpt-commits: 5b24cbf8560bc359a96872c2df2f902559b9b189
wpt-pr: 27583
Automatic update from web-platform-tests
[TablesNG] Implement column track merging
One the a11y requirements was that tables should do track merging.
I've skipped implementing this initially because there was major
disagreement about what to do.
This implementation follows the standard.
Columns defined by TD or COL are merged for table-layout:auto,
and not merged for table-layout:fixed.
Legacy did not follow the standard for columns defined by TDs:
they were always merged. Firefox implementation was closer to
standard, but sometimes buggy.
This changes results of some tests. Almost all of them are because
"TablesNG is more standards compliant", and new renderings match
FF.
There is disagreement about treatment of empty rows between
FF and TablesNGNG.
external/wpt/css/css-tables/html5-table-formatting-1.html
external/wpt/css/css-tables/html5-table-formatting-2.html
The rest of the changes render better, just like FF.
Two new tests have been added:
wpt/css/css-tables/column-track-merging.html
tests the standard.
accessibility/table-column-track-merging.html
tests Chrome's a11y API.
Change-Id: Ia222351f7c500963ace556d76c26fcefb1df24e1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2670193
Commit-Queue: Aleks Totic <atotic@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852958}
--
wpt-commits: 6902c0348cafb66a237b5ce75d9b3038bd3f3f87
wpt-pr: 27451
Automatic update from web-platform-tests
Add error message for keyDown and keyUp actions in testdriver-vendor.js
There are some actions that testdriver Action function supports when
the tests are running on wpt serve, but not when running on content
shell, such as keyDown and keyUp.
I add an error messages to resources/testdriver-vendor.js to
inform people to not use keyDown and keyUp actions in web tests.
Bug: 1174386
Change-Id: Ia723383fac948a1611d54aff7b9dd6f7e187d009
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2673923
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Philip Jägenstedt <foolip@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852929}
--
wpt-commits: 634384fb5674ec7185ce491911f06dc766db80c0
wpt-pr: 27498
Automatic update from web-platform-tests
webrtc wpt: do not use assert in helper function
this spams the testharness log of assertions a test runs
BUG=None
Change-Id: Ib14a7d45f3e18723a667ac292ecb3bdfd2e64ce3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2649933
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Cr-Commit-Position: refs/heads/master@{#852848}
--
wpt-commits: 7ac29511f2edf0203af1911013017f2c6598f035
wpt-pr: 27336
Automatic update from web-platform-tests
Implement the beginnings of "light dismiss" behavior for <popup>
With this CL, clicking outside a popup will dismiss that popup,
along with all others in the popup stack. Clicking within a
popup will preserve that popup in the visible state, but will
hide any popups above that popup in the stack.
Bug: 1168738
Change-Id: Ibb8fc90ba19929a04d746fbf092001f546fb1e75
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2683092
Auto-Submit: Mason Freed <masonfreed@chromium.org>
Reviewed-by: Ionel Popescu <iopopesc@microsoft.com>
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852844}
--
wpt-commits: 11b221b929db4793bc273cfdf96e85c7ef277a5a
wpt-pr: 27572
Automatic update from web-platform-tests
Implement CSSOM CSSCounterStyleRule API setters (p1)
This patch implements the framework for CSSCounterStyleRule setters
and invalidations:
1. If the value is valid, setter modifies the underlying
StyleRuleCounterStyle, increments its version number and mark counter
styles need update
2. During counter style update, CounterStyles are marked dirty if its
underlying StyleRuleCounterStyle has been changed (detected by
version checking).
Then we use to the existing dirtiness-marking and invalidation code path
for the remaining job.
This patch also implements setters for the following attributes:
- negative
- prefix
- suffix
- pad
- range
- fallback
- speakAs
Other attributes require are more complicated and will be implemented
in follow-up patches.
Bug: 687225
Change-Id: Ic9ceacf19da1c3739f98c80dde07814784258649
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2686322
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Commit-Queue: Xiaocheng Hu <xiaochengh@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852835}
--
wpt-commits: 4edc28a24eebd5308176cd875cdb4ac1ee467f8e
wpt-pr: 27560
Automatic update from web-platform-tests
Fix the Pointerevents IDL WPT test
Right now, the pointerevents IDL WPT test has errors of calling
"setPointerCapture", "releasePointerCapture" and "hasPointerCapture"
functions on document, because these three functions are defined in
"Element", and "Document" is not a subclass of "Element". That is why we
see the errors, such as "FAIL Element interface: document must inherit
property "setPointerCapture(long)" with the proper type assert_inherits:
property "setPointerCapture" not found in prototype chain".
I fixed it by changing the "document" to "document.body", which is an
element.
Bug: 1163370
Change-Id: I2435466e76fee05235d135e6181a566c898a5855
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2685361
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852833}
--
wpt-commits: d0f2ce4b18d7a07fe9771605a293fdbb7a5200f8
wpt-pr: 27577
Automatic update from web-platform-tests
Add WPTs and minor impl fixes for xr light estimation
Adds WPTs around expected behavior for the WebXR Light Estimation spec.
Also corrects a few cases where getReflectionCubeMap should have thrown
an exception but did not currently.
Change-Id: I3e3393c3911a83bdfc91463cf614e04a31dba009
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2685615
Commit-Queue: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Brandon Jones <bajones@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852756}
--
wpt-commits: 43ead8133543f5d38c0f7aae65770bc1d2e8bad7
wpt-pr: 27557
Automatic update from web-platform-tests
Treat huge 'repeatCount' values as invalid
String::ToDouble() can return infinity. This value could either be
treated the same as the 'indefinite' keyword or as invalid. Gecko
appears do the latter so follow suit.
Bug: 1176608
Change-Id: Ia945404711f7580bcbabded076904205e00b2564
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2685176
Reviewed-by: Stephen Chenney <schenney@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#852720}
--
wpt-commits: 89400e4064b5f59e22f0fc63b3b6f7994f946c66
wpt-pr: 27573
Automatic update from web-platform-tests
SVG parsing allows calc() for <number>
The SVG spec says[1] to allow <number> when parsing values for
presentation attributes to allow unitless lengths for things like
font-size in the attribute.
The CSS specification says calc() with numbers is allowed wherever
<number> is allowed. Blink is the only browser to allow calc()
expressions for <number>. It is possible we should change that, but as
long as we accept it at parse time, we should handle it when applying it
to the ComputedStyle.
This CL computes font-size lengths for calc() expressions with numbers.
[1] https://svgwg.org/svg2-draft/types.html#syntax
Bug: 1172750
Change-Id: Ic20645d96b898c359d55eadfe902af0ac37a1dfa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2685172
Reviewed-by: Fredrik Söderquist <fs@opera.com>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852650}
--
wpt-commits: ef69b81f39829fbb1acec84b17b99640b05fd8e7
wpt-pr: 27569
Automatic update from web-platform-tests
Make responsexml-document-properties.htm timezone correct
The web platform test responsexml-document-properties.htm was flaky,
apparently due to incorrect handling of timezones. Make the timezone
handling robust to fix the flakiness.
BUG=1144537
Change-Id: Ib338d7b9e87415a4900963782fde218b0d3ec6b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2684076
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852607}
--
wpt-commits: 4cf1a9640f6c87c31b21c115d8e4fce2cfffa427
wpt-pr: 27561
Automatic update from web-platform-tests
New test for buttons with percentage children (#27520)
Both Blink and WebKit implement buttons as flexboxes, which in this case, wrap the child in an anonymous box. Anonymous boxes are skipped when computing percentage heights but we need to ensure that their children with percentage heights are properly sized.
--
wpt-commits: e7a87a22ecca336956900428121a8094c835a5b3
wpt-pr: 27520
Automatic update from web-platform-tests
Reorganize and augment beacon wpt
- Run tests on secure contexts. I'm planning to use the sec-fetch-mode
header once WebKit supports it, which is only available on secure
contexts.
- Replace html files with window.js files.
- Merge many beacon-basic-* files into beacon-basic.https.window.js.
This is doable because the payload size limit is per context, not
per page.
- Merge beacon-readablestream.js and beacon-error.sub.window.js into
beacon-basic.https.window.js.
- Merge beacon-preflight-failure.sub.window.js into
beacon-cors.https.window.js.
- Add more cross origin tests in beacon-cors.https.window.js.
- Slim down beacon-common.sub.js.
Also remove some test files in http/tests/sendbeacon, because they are
covered by wpt/beacon.
Bug: 720303
Change-Id: Id65c70d290753428d5d17bc8e9e783969ff8bc16
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2677465
Commit-Queue: Yutaka Hirano <yhirano@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852515}
--
wpt-commits: a341862f7bf55470eb456fbdbb20e465508e7cb9
wpt-pr: 27512
Automatic update from web-platform-tests
[LayoutNG] Containing block offset during nested fragmentation
The containing block offset should be the offset from the top of the
inner multicol to the start of the containing block (as if all of the
columns are placed one on top of the other). When propagating OOFs
in a nested fragmentation context, we miss the block contribution
from columns in previous outer fragmentainers.
To fix this, add the block size for such previous columns to the
OOF containing block offsets. And since the static position is
adjusted based on the containing block offset, fixing this for the
containing block offset also fixed the issue with the static position.
Bug: 1079031
Change-Id: Idd561cfb8ca01b4248da5c94933464fd1abe3a0d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2680070
Commit-Queue: Alison Maher <almaher@microsoft.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852421}
--
wpt-commits: e2e7e68a4b179250de7eb3fb71c81d098c20fd0c
wpt-pr: 27554
Automatic update from web-platform-tests
Not all inline break tokens have ComputedStyle.
This has been the case ever since the ComputedStyle field was added:
https://chromium-review.googlesource.com/846585
AddBreakBeforeChild() in NGFragmentBuilder (since moved to
NGBoxFragmentBuilder) passes nullptr for ComputedStyle.
So just add a nullptr check.
Bug: 1175666
Change-Id: Ie0d46c93a64f25de09f3193c5cb329e9ac37b88b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2683984
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852354}
--
wpt-commits: a13d98ce6f8023a121131db9095454e42da4ec5b
wpt-pr: 27545
Automatic update from web-platform-tests
Remove some non-standard test cases from a counter style WPT test
WPT css/vendor-imports/mozilla/mozilla-central-reftests/counter-styles-3/redefine-attr-mapping.html
tests the "type" attribute on <ul>, <ol> and <li> tags, which is
non-standard other than values "i", "I", "a" and "A" on <ol> [1].
Firefox and Chrome have implemented different sets of non-standard
type values on these tags. The test is currently asserting Firefox's
behavior.
This patch removes some of the non-standard test cases, and leaves
the common implemented subset between Firefox and Chrome, so that we
can also pass the test.
[1] https://html.spec.whatwg.org/multipage/grouping-content.html#attr-ol-type
Bug: 687225
Change-Id: I855f9d4e50bdc3cae0c03cc87b66081bd39c88a8
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2684619
Auto-Submit: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Anders Hartvoll Ruud <andruud@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852316}
--
wpt-commits: 08d4723607039bae9981039dd99bf2b0bdd86b78
wpt-pr: 27552
Automatic update from web-platform-tests
Allow webview shell package name to be passed in through command line (#27551)
The activity name will still be hard coded, as that is defined
in Java file, and not impacted by any gn args
Bug: 1170171
--
wpt-commits: f6763c716b029770e090ad4ee9472aaf5f3f8614
wpt-pr: 27551
Automatic update from web-platform-tests
Revert "Update registration-schedule-job.https.html to reflect the spec"
This reverts commit cf04532ef9c4b904f22d1307bd924b90bbbe4ddb.
Reason for revert: The test started failing on mac after CL landed:
https://ci.chromium.org/ui/p/chromium/builders/ci/Mac10.12%20Tests/41681/overview
Original change's description:
> Update registration-schedule-job.https.html to reflect the spec
>
> Previously, the test expectation didn't comply with the spec because it
> expected there's an installing worker even if register() actually didn't
> install a new worker.
> This CL is to update the expectation to wait for each register() call
> resolved one by one. This should work because each job must not be
> coalesced so the states should be updated correctly when those promises
> are resolved.
>
> Bug: 979593
> Change-Id: Ib3874e7e15ebb0dfa5608cc2ff4d3484cffd72b2
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2679094
> Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
> Reviewed-by: Asami Doi <asamidoi@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#852157}
TBR=shimazu@chromium.org,chromium-scoped@luci-project-accounts.iam.gserviceaccount.com,asamidoi@chromium.org
Change-Id: Icb7c609f6b8a44b55ae338255058679d7fa55624
No-Presubmit: true
No-Tree-Checks: true
No-Try: true
Bug: 979593
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2684257
Reviewed-by: Christian Dullweber <dullweber@chromium.org>
Commit-Queue: Christian Dullweber <dullweber@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852210}
--
wpt-commits: 154ecbab5c518e5c19d5429ef46c5847c2b6fce6
wpt-pr: 27549
Automatic update from web-platform-tests
Use OOP-R texture readback in ReadbackTextureBackedFrameToMemorySync
This utility function is now used by webrtc video frame adapter with a
shared RasterContextProvider, which usually supports OOP-R and not GLES2.
This CL adds a path for that case. Absence of gr_context is used as a signal
to use OOP-R mode.
Bug: 1132965,1156408
Change-Id: Ic75d52f8406945ffbecfa8d3c65f08090f26381e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2678002
Commit-Queue: Ilya Nikolaevskiy <ilnik@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Reviewed-by: Dale Curtis <dalecurtis@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852173}
--
wpt-commits: 22a3c8461c1e2df11d5cc0de52486e8afed8bbbd
wpt-pr: 27503
Automatic update from web-platform-tests
Update registration-schedule-job.https.html to reflect the spec
Previously, the test expectation didn't comply with the spec because it
expected there's an installing worker even if register() actually didn't
install a new worker.
This CL is to update the expectation to wait for each register() call
resolved one by one. This should work because each job must not be
coalesced so the states should be updated correctly when those promises
are resolved.
Bug: 979593
Change-Id: Ib3874e7e15ebb0dfa5608cc2ff4d3484cffd72b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2679094
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Asami Doi <asamidoi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852157}
--
wpt-commits: 6cd5f63fb98c42d7c1e79a4e2db84b970e7fb86d
wpt-pr: 27519
Automatic update from web-platform-tests
[TablesNG] clusterfuzz: inconstistent NG/Legacy tree
When:
- DIALOG has display:table-row-group
- DIALOG is forced into Legacy layout.
- DIALOG gets shown with showModal.
We end up with a
LayoutNGTable
LayoutTableSection
This is because CreateAnonymousTableWithParent gets a hint
of whether it should be NG or Legacy from parent (#document),
and not its future child (LayoutTableSection).
Fix: pass through a variable to force legacy if needed.
Bug: 1175222
Change-Id: I7898f70f9a8d98797d4289bb3050c82514010033
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2683044
Auto-Submit: Aleks Totic <atotic@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852153}
--
wpt-commits: d229da2bd2a1524036a3286e03b50a6a48216836
wpt-pr: 27537
Automatic update from web-platform-tests
webrtc: update addIceCandidate() call to match spec
see https://w3c.github.io/webrtc-pc/#interface-definition
This allows addIceCandidate() as end-of-candidates indication. This is
not yet implemented at the native layer.
BUG=chromium:978582
Change-Id: Id0f2acd2dcfdf4f5d311437df22c178c9d69630d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2680823
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Reviewed-by: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Cr-Commit-Position: refs/heads/master@{#852128}
--
wpt-commits: 8d1dba2aa6fe9cd79c98f4b83f04145a00cfbe2b
wpt-pr: 27517
Sebastian Hengst
Andrew McCreight
Emilio Cobos Álvarez
James Graham
Pierre TALLOTTE
moz-wptsync-bot
Thiemo Nagel
Philip Jägenstedt
Daniel Clark
Eugene Zemtsov
Aleks Totic
Lan Wei
Philipp Hancke
Mason Freed
Xiaocheng Hu
Aaron Krajeski
Alexander Cooper
Fredrik Söderqvist
autofoolip
Rune Lillesveen
Manuel Rego Casasnovas
Adam Rice
Sergio
Yutaka Hirano
Alison Maher
Morten Stenshorne
WeizhongX
Kagami Sascha Rosylight
Christian Dullweber
Ilya Nikolaevskiy
Makoto Shimazu
Findit