Automatic update from web-platform-tests
CSS: Retire expansion-based implementation of :is and :where
We no longer attempt to expand :is and :where during style sheet loading.
Correct support for these selectors remains to be implemented.
In particular, we need:
- invalidation - RuleFeatureSet
- support for empty selector lists
- error recovery - CSSSelectorParser
Bug: 1127347
Change-Id: I28912cf5cb9b373c423d488b47c20251917329fe
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405034
Commit-Queue: Eric Willigers <ericwilligers@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808207}
--
wpt-commits: 140c8a2c352df047d2e60bfdef1169364daf2af7
wpt-pr: 25507
Automatic update from web-platform-tests
Custom layout needs to force NG layout for the subtree.
Just like for MathML, custom layout (display:layout()) has no legacy
layout engine implementation, so we need to force NG layout, even when
contained by something that requires legacy fallback.
Rewrote the mechanism somewhat; calling ComputedStyle() on an element
isn't the right thing to do within Element::ShouldForceLegacyLayout()
(it called ShouldForceNGLayout(), which did that), since
ShouldForceLegacyLayout() is involved when style is about to change, or
when it has just been changed. ShouldForceLegacyLayout() will now
return true even if the display type requires LayoutNG. Cope with this
by just not setting ForceLegacyLayout on any NG LayoutObjects at all.
And remove a couple of DCHECKs in NG LayoutObject classes that expected
legacy fallback not to be in use on the Element side.
This is rather convoluted. :(
Also update HTMLSlotElement::AttachLayoutTree(), which recently got
modified to support legacy fallback properly.
This fixes one of three DCHECK failures that occur in the fuzzer test
in bug 1127112.
Bug: 1127112
Change-Id: I16b5f5297cb04192056f6c5137c2cefa1bc33298
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414289
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Frédéric Wang <fwang@igalia.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808311}
--
wpt-commits: 4811c33c5a6bc404ccbf334fca80d316bb3d916b
wpt-pr: 25575
Automatic update from web-platform-tests
[WPT] Add tests for Worker.terminate() during worker script evaluation
workers/Worker-terminate-forever.html
terminates workers just after construction, and thus it's likely
that the workers are terminated before script evaluation is started.
This CL adds Worker-terminate-forever-during-evaluation.html
that waits for postMessage(), to ensure the worker is terminated
after script evaluation is started.
Bug: 1111134, 1129785
Change-Id: I9ebc8effe6234a297e0851042f5de41f611d55aa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2355160
Commit-Queue: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808304}
--
wpt-commits: d1c32457e97d9147803705abc4ffac424733dd8d
wpt-pr: 25004
Automatic update from web-platform-tests
bluetooth: Add optionalManufacturerData to options
This change adds the RequestDeviceOptions.optionalManufacturerData
property in order to enable manufacturer data to be protected behind
this permission.
This change also enforces the filtering of service and manufacturer data
from BluetoothAdvertisingEvent objects if services and manufacturer
codes are not included in the filters, optionalServices, and
optionalManufacturerData fields of the RequestDeviceOptions object.
Bug: 1108958
Change-Id: Id7f546e3be5b3c3c26538a69f810a33d2a446fb6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2389243
Commit-Queue: Ovidio de Jesús Ruiz-Henríquez <odejesush@chromium.org>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Martin Barbella <mbarbella@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808118}
--
wpt-commits: b8e402ff503177931c5bfffbeccde666acffe31e
wpt-pr: 25351
Automatic update from web-platform-tests
[mathml] Only perform special handling of <mo>s when they are text-only
MathML Core says special properties of operators happen when the
corresponding <mo> elements contain text content only [1]. However,
Blink currently just reads the element's textContent() without checking
whether it contains non-text children. This CL fixes that behavior and
also adds a WPT test to verify correct lspace/rspace (including after
dynamic change of the <mo> content).
[1] https://mathml-refresh.github.io/mathml-core/#dfn-algorithm-for-determining-the-properties-of-an-embellished-operator
Bug: 6606
Change-Id: Iab0e3309bf03167889e4a7161fd053a4a9744908
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414282
Commit-Queue: Frédéric Wang <fwang@igalia.com>
Reviewed-by: Rob Buis <rbuis@igalia.com>
Cr-Commit-Position: refs/heads/master@{#808089}
--
wpt-commits: 43454a84279c7400343aaabb09f6278b08293623
wpt-pr: 25590
Automatic update from web-platform-tests
[LayoutShiftTracker] Fix contain:paint
We should check ShouldClipOverflow() instead of IsScrollContainer()
(which was renamed from HasOverflowClip() recently -- this CL shows how
the new name improved code readability) for inclusion of layout overflow
for layout shift tracking.
Bug: 1127474
Change-Id: Id85b292b65dae837d1e366d548939b85c9cd5d5b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2417061
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808087}
--
wpt-commits: fb7851d911cead272a82feacbcc92983b5ad51a7
wpt-pr: 25603
Automatic update from web-platform-tests
idle-detection: Implement requestPermission() method
This change implements a static requestPermission() method on the
IdleDetector interface and switches the API from requiring the
"notifications" permission to the new "idle-detector" permission.
Bug: 878979
Change-Id: If2162f6a1f770544aeb82f98fcc65a76059b7d13
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2359539
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Reviewed-by: Ayu Ishii <ayui@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808019}
--
wpt-commits: 80c4b6a039de41d75eec3845fec5fc8ade50c390
wpt-pr: 25399
Automatic update from web-platform-tests
Prevent break opportunity offset to surpass the item's range_end
When exploring breaking opportunities we were early return, and shaping
to the end, when we detected that current candidate overflow and next
breaking opportunity surpass the item's range end.
However, since we landed in r807457 the new TextBreakIterator's
behavior of breaking always after the space run, we can get some
opportunities that surpass the item's range_end even if the candidate
doesn't overflow. An example of this could be when trailing spaces are
located in different items.
This patch ensures that even when the candidate doesn't overflow, we
never consider breaking opportunity offsets that surpass the item's
range end; since we are not overflowing, we'll proceed with the shaping
logic considering range_end as maximum of the breaking opportunity
offset.
Bug: 1128571
Change-Id: I704eb8091cdca00713fed15e22749bb633bacc71
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414196
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#808007}
--
wpt-commits: 0293b6f415e8d8a869462bbf3f3f5bdeb3f268db
wpt-pr: 25601
Automatic update from web-platform-tests
Add tentative WPT for Schemeful Same-Site
Adds new tests for Schemeful Same-Site along with a virtual test suite
which enables the SchemefulSameSite feature.
Because Schemeful Same-Site only modifies the definition of "same-site"
it's adequate to test only a few cases that confirm the expected
same-siteness rather than try to thoroughly test all possible
`SameSite` situations.
Bug: 1127348
Change-Id: I9b914dd425bfb8cda6fc1ddc9f3606940f0b9a1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412907
Commit-Queue: Steven Bingler <bingler@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807923}
--
wpt-commits: 1f676491f8e083426cb35e431076bc7e023be4a4
wpt-pr: 25552
Automatic update from web-platform-tests
Feature/media capture fitness distance (#25493)
* Fix getUserMedia tests to match descriptions
* Add a Media Capture fitness distance test
--
wpt-commits: 92053e18df72ae322c32af7873678acfd0865a7a
wpt-pr: 25493
Automatic update from web-platform-tests
HTML: make sure the default opacity of ::placeholder is 1
--
wpt-commits: a5d0e1a4faf9d1a04d93ed148a90dc820283a1db
wpt-pr: 25310
Automatic update from web-platform-tests
wpt: add pointer about webrtc/h264 failures on buildbots
as buildbots missing H264 comes up frequently.
BUG=chromium:840659
Change-Id: I8db4bee8bbbc04d1227d957dcd6a73ee658ec829
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414315
Reviewed-by: Harald Alvestrand <hta@chromium.org>
Commit-Queue: Philipp Hancke <philipp.hancke@googlemail.com>
Cr-Commit-Position: refs/heads/master@{#807850}
--
wpt-commits: 57cb5de37d282d455c9b87f70dfff930924221a2
wpt-pr: 25589
Automatic update from web-platform-tests
Modernize WPT: resource-timing and navigation-timing.https.html
As a part of the effort to understand the current behavior of the
resource timing, I changed the tests to use async/await for readability
with adding a few comments.
Bug: 1128786
Change-Id: I45daee67e52a13c98ad3f2010131d858a58781d3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413927
Commit-Queue: Makoto Shimazu <shimazu@chromium.org>
Auto-Submit: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807845}
--
wpt-commits: b1de454b0cefc8e140ae8824d27251e1e5fb4b60
wpt-pr: 25563
Automatic update from web-platform-tests
Fieldset NG: Fix hit-testing for the rendered LEGEND, take 2
crrev.com/806924 missed to add |accumulated_offset| to the LEGEND's
offset. So hit-testing didn't work well if the FIELDSET was placed far
from the origin.
Bug: 1127743
Change-Id: I16c80b8074f9082516a6ecd5bb82407bbe7d3551
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2413681
Auto-Submit: Kent Tamura <tkent@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807797}
--
wpt-commits: 7efc87788ce63b7a6123b3b0466d89a9e3433f39
wpt-pr: 25580
Automatic update from web-platform-tests
Don't allow legacy list item markers inside an NG subtree.
We usually don't encounter NG objects inside a legacy layout subtree,
but this may happen when we have display types that aren't implemented
in the legacy engine, e.g. MathML and custom layout.
This situation should be rare enough, and the combination of list items
and MathML / custom layout doesn't seem like a very common use case. So
just don't go there, and instead keep looking for a better candidate to
place the list item marker inside.
Bug: 1127112
Change-Id: I74c39fae7e5c48d73d5603efca486a05c234a25a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414268
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807788}
--
wpt-commits: f52771d163bcd9e12ea3903f48478ddaa5cdbe3b
wpt-pr: 25574
Automatic update from web-platform-tests
Increase event wait time for isInputPending WPTs
To reduce flakiness of positive isInputPending tests, wait for 500ms rather
than 200ms in an attempt to mitigate queueing delay variance.
Bug: 910421, 1124978, 1126853
Change-Id: I3136cdc0941b427c97c15de8969d7bbe243b4218
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2415137
Reviewed-by: Nicolás Peña Moreno <npm@chromium.org>
Commit-Queue: Andrew Comminos <acomminos@fb.com>
Cr-Commit-Position: refs/heads/master@{#807693}
--
wpt-commits: e48be6d08b272744fe6d1d28e91a5808cf92fb68
wpt-pr: 25577
Automatic update from web-platform-tests
Add XR support to video.rVFC
Currently, when we enter an immersive XRSession, window.rAF calls stops,
which means we no longer deliver video.requestVideoFrameCallback calls.
This CL adds video.rVFC support to immersive XRSessions. If we find an
immersive XRSession, we schedule video.rVFC callbacks there instead of
the ScriptedAnimationController (SAC).
There can only be one immersive XRSession. If we don't find a session,
but we find that the XRFrameProvider exists, we request to be notified
when an immersive session start. This allows us to keep callbacks going
if the callbacks were already scheduled in the SAC when starting an
XRSession. Simmilarly, if the session ends when callbacks were pending
in the XRSession, we reschedule ourselves in the SAC.
Bug: 1107578
Change-Id: If0acf9445bb789bc848e0043908fc9b769cc5bdd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2406522
Commit-Queue: Thomas Guilbert <tguilbert@chromium.org>
Reviewed-by: Klaus Weidner <klausw@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807653}
--
wpt-commits: 54df2c65fcd287a4710e802b100c7e18a7a9901d
wpt-pr: 25555
Automatic update from web-platform-tests
[Document Policy] Isolate font-display wpt tests
This CL splits font-display tests into smaller individual tests. The
split has following benefits:
- Clear obstable for implementation of violation report deduplication
- Make the tests stricter. Before the test can verify there are
4 violation reports generated, but cannot tell which 4 cases generate
violation reports.
Previously there was an attempt on isolating tests into subframes
(https://chromium-review.googlesource.com/c/chromium/src/+/2227863),
but failed due to flaky crash in network cache (crbug.com/1087277).
Bug: 1087277
Change-Id: Ifad35b40d112956fb00fd680b329e539a8762ed9
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2405916
Commit-Queue: Charlie Hu <chenleihu@google.com>
Reviewed-by: Jason Chase <chasej@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807589}
--
wpt-commits: 4a13ee142da1e5d1d089679eacc8062dc081f627
wpt-pr: 25518
Automatic update from web-platform-tests
[COOP] access reporting: Add same-origin/cross-origin variant.
Soon, the reports will contains URLS about the other document:
- openeeURL
- openerURL
- otherDocumentURL
- referrer
- initialPopupURL
Depending on whether they are same-origin or cross-origin with the
reporter document, they might be reported or not.
This patch add a same-origin/cross-origin variant for every type of
accesses.
Bug: 1090273
Change-Id: Ieeb396f6220877a2a61541cb33a964261e5f4070
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2407314
Reviewed-by: Pâris Meuleman <pmeuleman@chromium.org>
Commit-Queue: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807470}
--
wpt-commits: d751285bded743ea6dfa68365dafb0d30f29a9c3
wpt-pr: 25512
Automatic update from web-platform-tests
[webnfc] Remove id, recordType, and mediaType from NDEFScanOptions.
Origin Trial feedback was that webNFC is better without filtering.
NDEFScanOptions now does not need to carry information like recordType
or mediaType as we are not matching them against active watchers
anymore.
Spec changes:
https://github.com/w3c/web-nfc/issues/560https://github.com/w3c/web-nfc/pull/565
Bug: 520391
Change-Id: I642cff9e72745728f41ad74e803d971a3126ddad
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2401020
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com>
Cr-Commit-Position: refs/heads/master@{#807597}
--
wpt-commits: 559818b1ed95b45b5119420e942e6c04e8816fa7
wpt-pr: 25523
Automatic update from web-platform-tests
[WIP] Attempt to fix escaping in CSP tests
{{GET}} is automatically HTML-escaped (*not* URL-encoded) when used in
`.sub.html`. There is some insufficient workaround in this test suite
for things like < >. This PR attempts to properly decode HTML entities.
--
wpt-commits: 70f1fc9aa9519abd3f4ca5d114d02c004b4764b3
wpt-pr: 25275
Automatic update from web-platform-tests
[css-flex] Slight refactor to how table flex items are handled
* Don't make all tables in row flexboxes go through the min-width:auto
path, which was added in
https://chromium-review.googlesource.com/c/chromium/src/+/2392444
* Always make flex item's min/max widths encompass table's min
intrinsic size, even if the table has a definite min-width.
No behavior change intended.
Change-Id: I92456b5c4e20272887066593d166809e6b98ab54
Bug: 1123100,1128262
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410596
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807492}
--
wpt-commits: 1bffae481e8a6a4e89063b6a3cacd4851691517f
wpt-pr: 25529
Automatic update from web-platform-tests
Reland "New TextBreakIterator's default behavior breaks after space run"
This is a reland of 1cb4c9a70836c34cc0d5260902f71d3e8a2f67ec
Rebaselined a few tests for mac 10.14 and 10.15.
Original change's description:
> New TextBreakIterator's default behavior breaks after space run
>
> Before this change, we were considering breaking opportunities before
> space runs. This approach allowed us to avoid re-shaping in many cases,
> which has an important advantage in terms of performance.
>
> However, the Unicode spec (UAX#14) state that breaking before a space
> character is not allowed [1], so we had to implement this logic after
> our TextBreakIterator had already determined the best breaking
> opportunity. This approach has been working fine so far for regular
> spaces (white-space, tabs, ...), but it doesn't work correctly for
> other BA [2] class characters; in the CSS Text specification, these are
> known as "other space separators" [3].
>
> In order to implement the correct behavior for any kind of space, we
> would need to change our TextBreakIterator implementation so that
> matches the Unicode rules, considering breaking opportunity after
> space runs. This change should also consider the performance impact
> of the extra re-shaping operations required to deal with trailing
> spaces.
>
> In order to prevent performance regressions, we'll store the position
> of the 'end of non-hangable run', which will be used in case of items
> with styles dictating rules to collapse trailing spaces.
>
> [1] https://unicode-org.atlassian.net/browse/ICU-20843
> [2] https://www.unicode.org/reports/tr14/tr14-39.html#BA
> [3] https://drafts.csswg.org/css-text-3/#other-space-separators
>
> Change-Id: Ie4a3890c75a3faff1a0155d4a40bcaa85bc6ac06
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2047943
> Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
> Reviewed-by: Koji Ishii <kojii@chromium.org>
> Cr-Commit-Position: refs/heads/master@{#806928}
Change-Id: I9b5204f0b2e49367ab7d7a2107900763844fd2bb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412307
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807457}
--
wpt-commits: 514994209e0261e6d234398f2b2ca8bdf90db68a
wpt-pr: 25546
Automatic update from web-platform-tests
Reland "[mathml] Use post.underlineThickness for the default fraction rulethickness"
This was reverted because the frac-1 test is failing on all windows platform
not just Win10.
Original change's description:
> Revert "[mathml] Use post.underlineThickness for the default fraction rulethickness"
>
> This reverts commit d01e107517ff5b1da0544be36c5caaf30c27456e.
>
> Reason for revert: <breaks win7 bots - https://ci.chromium.org/p/chromium/builders/ci/Win7%20Tests%20%281%29>
>
> Original change's description:
> > [mathml] Use post.underlineThickness for the default fraction rulethickness
> >
> > MathML Core currently defines fallback values to use when no MATH table
> > is available. This CL performs the remaining work to ensure fractions
> > align with the specification. It also adds WPT test to check these
> > fraction fallback parameters, although testing them extensively is
> > difficult.
> >
> > Bug: 6606, 1058369
> > Change-Id: Ic916c0c4b925674d526d78989988e57d8735bf4e
> > Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2410384
> > Commit-Queue: Frédéric Wang <fwang@igalia.com>
> > Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
> > Cr-Commit-Position: refs/heads/master@{#807083}
>
> TBR=ikilpatrick@chromium.org,fwang@igalia.com,rbuis@igalia.com
>
> Change-Id: Ia8857539d69bbbafda2be5501ac1b766488be77d
> No-Presubmit: true
> No-Tree-Checks: true
> No-Try: true
> Bug: 6606
> Bug: 1058369
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2412750
> Reviewed-by: David Bienvenu <davidbienvenu@google.com>
> Commit-Queue: David Bienvenu <davidbienvenu@google.com>
> Cr-Commit-Position: refs/heads/master@{#807144}
Bug: 6606, 1058369
Change-Id: I2fefb18b84c9604fcd40a013617a51aeadf56602
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2414029
Reviewed-by: Rob Buis <rbuis@igalia.com>
Commit-Queue: Frédéric Wang <fwang@igalia.com>
Cr-Commit-Position: refs/heads/master@{#807437}
--
wpt-commits: 96f4c502e75f34ddf8bdd1aea38c0d01a69b69e0
wpt-pr: 25565
Automatic update from web-platform-tests
sensors: Stop using "reading" events to check if a sensor is suspended.
Tests using generic-sensor-iframe-tests.sub.js have been flaky on the
Mac bots for a long time. The flakiness is usually seen in the
same-origin iframe focus traversal test, where the "is_sensor_suspended"
command returns true rather than false.
The cause is the same one as r805674 ("sensors: Rewrite the frequency
hint test"): the mock platform sensor uses window.setInterval() to
simulate the periodic reading of sensor data, but setInterval()'s actual
frequency can vary a lot (especially on the Mac bots), to the point that
we cannot rely on the other timer we created in
iframe_sensor_handler.html will consistently have a period longer than
setInterval()'s.
The only way to reliably check if a sensor is suspended or not is to
query the mock platform sensor directly at the expense of no longer
using only the public API: we now have a isReadingData() method in
MockSensor that we use to query if the sensor is fetching new readings
or not.
Bug: 1073865
Change-Id: I99941b88722fc68163cca54e44ac6fc61a6425cc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2411933
Commit-Queue: Raphael Kubo da Costa <raphael.kubo.da.costa@intel.com>
Reviewed-by: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#807421}
--
wpt-commits: 394d8987894db85f85b1746b606419e1c88505e4
wpt-pr: 25534
Eric Willigers
autofoolip
Morten Stenshorne
Hiroshige Hayashizaki
Wei Lee
moz-wptsync-bot
youennf
Shik Chen
Ovidio Henriquez
Frédéric Wang
Xianzhu Wang
Reilly Grant
Javier Fernández García-Boente
Steven Bingler
Adam Argyle
Eero Häkkinen
Karl Dubost
Philipp Hancke
Makoto Shimazu
Palak Agarwal
Kent Tamura
Harald Alvestrand
Tyler Wilcock
Andrew Comminos
Thomas Guilbert
Charlie Hu
arthursonzogni
Arnaud Mandy
Robert Ma
David Grogan
Stephen McGruer
Philip Jägenstedt
Raphael Kubo da Costa
ziransun