Automatic update from web-platform-tests
[WebNFC] Add data attribute to NDEFRecord
This CL adds the data attribute to NDEFRecord as specified in
https://github.com/w3c/web-nfc/pull/379
Bug: 520391
Change-Id: Icab2c69d6cec95540e6f8525354e86a6937aa4e6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1871369
Reviewed-by: Rijubrata Bhaumik <rijubrata.bhaumik@intel.com>
Reviewed-by: Mike West <mkwst@chromium.org>
Commit-Queue: François Beaufort <beaufort.francois@gmail.com>
Cr-Commit-Position: refs/heads/master@{#708167}
--
wpt-commits: ad93565efd7161ee146a44e92c02d7339dbaf8e1
wpt-pr: 19804
Automatic update from web-platform-tests
Convert tabs to spaces in directories with few lint errors (#19824)
To find the candidates for this change, the "INDENT TABS" exceptions
in lint.whitelist were removed and ./wpt lint` run.
The output was piped through `grep '^ERROR:lint:' | cut -d: -f3 | sort
| uniq | cut -d/ -f1 | uniq -c | sort -n`, giving the following list:
```
1 pointerlock
1 shadow-dom
1 webaudio
2 docs
2 webvtt
7 content-security-policy
9 encoding
203 conformance-checkers
5011 css
```
Based on that, conformance-checkers, css and encoding were left alone.
--
wpt-commits: 3abb74d89e92b91567d16653e0b63d27f15a7022
wpt-pr: 19824
Automatic update from web-platform-tests
Replace "TaskCluster" with "Taskcluster" where possible (#19822)
This matches the Taskcluster website and our label:
https://tools.taskcluster.net/https://github.com/web-platform-tests/wpt/labels/Taskcluster
Command use:
> git grep -l TaskCluster | xargs sed -i 's/TaskCluster/Taskcluster/g'
Occurences in tools/taskcluster/testdata/ were left alone, as they
match real historical commits/PRs with "TaskCluster" in them.
--
wpt-commits: 237825fc22f06ca12a3bff5011a668ce0f101a7c
wpt-pr: 19822
Automatic update from web-platform-tests
Don't generate pseudo element inside display:none.
We checked for non-null GetComputedStyle(), but it may also be non-null
inside display:none when ensured from getComputedStyle(). Skip
generating pseudo elements for that case. This caused a DCHECK failure
due to an incorrect marking for layout tree re-attachment inside
display:none.
Bug: 1013570
Change-Id: I75318b9d3bed1ed68dab232d90bbdc9b68655152
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1872096
Reviewed-by: Xiaocheng Hu <xiaochengh@chromium.org>
Commit-Queue: Rune Lillesveen <futhark@chromium.org>
Cr-Commit-Position: refs/heads/master@{#708147}
--
wpt-commits: 03f4ea383cd4d9c5e8f46f9f405833e96a3a4809
wpt-pr: 19815
Automatic update from web-platform-tests
[Azure Pipelines] upgrade to Ubuntu 18.04 (from 16.04)
These jobs only run `./wpt test-jobs` and `curl`, but it's just as
well to upgrade them well before Ubuntu 16.04 is no longer supported.
--
wpt-commits: 0740bf536a0dbdb60ef76dd0cb15980ebcc86c7d
wpt-pr: 19820
This warns because an expression with a side effect is inside a `static_assert` or
`sizeof`.
Differential Revision: https://phabricator.services.mozilla.com/D51243
--HG--
extra : moz-landing-system : lando
The problem is that a GC can be triggered in a number of ways, so scheduling zones in nsJSContext::GarbageCollectNow is not effective. This patch schedules these zones in the GC callback, which is always called at the start of GC. This means we have to change the internal logic slightly to allow the GC callback to schedule addional zones; previously this state was saved and restored before/after running the callback.
Differential Revision: https://phabricator.services.mozilla.com/D51145
--HG--
extra : moz-landing-system : lando
The idea of these are not to penalize legit uses of scroll anchoring, and
catching pathological cases fast.
The current algorithm I thought of is just whether the average of all the
consecutive scroll anchoring adjustments is less than a given threshold.
If the average adjustment is close to zero and the user is not scrolling, it
means that we're not making much progress.
It is important that zero adjustments don't get counted, since those are common
during window resizes and don't have side-effects anyway.
Exact number may need tuning, let me know if you want it
nightly-and-early-beta-only for now or something.
Depends on D51038
Differential Revision: https://phabricator.services.mozilla.com/D51024
--HG--
extra : moz-landing-system : lando
This makes HeapPtr members const where it was easy to do so. Flagging jimb for review since most of these were in the debugger.
Differential Revision: https://phabricator.services.mozilla.com/D50624
--HG--
extra : moz-landing-system : lando
This replaces GCPtr members with const GCPtr where trival to do so.
Depends on D50618
Differential Revision: https://phabricator.services.mozilla.com/D50619
--HG--
extra : moz-landing-system : lando
The main change is to make BarrieredBase::unsafeUnbarrieredForTracing() const and use const_cast to get return the non-const pointer. This makes sense because the GC is allowed to update the pointer used while preseving the logical value of the cell, e.g. when compacting.
Differential Revision: https://phabricator.services.mozilla.com/D50618
--HG--
extra : moz-landing-system : lando
This warns because an expression with a side effect is inside a `static_assert` or
`sizeof`.
Differential Revision: https://phabricator.services.mozilla.com/D51243
--HG--
extra : moz-landing-system : lando
A null MixerCallbackReceiver in the AudioMixer callback list can create a crash when the AudioMixer::FinishMixing() is being called. Verify that the receiver is not null before adding it in the list.
Differential Revision: https://phabricator.services.mozilla.com/D51082
--HG--
extra : moz-landing-system : lando
This patch allows WR to dynamically choose whether picture caching
is enabled per-frame, rather than only during initialization.
This will allow mobile devices to disable picture caching during
pinch zoom events, where tiles will be constantly invalidated.
This can also be controlled via a debug flag, which allows dynamic
toggling of picture caching in both Gecko and Wrench. This is
useful for profiling, to compare direct rasterization to picture
caching performance.
The native compositor interface relies on picture caching. So, if
a native compositor is enabled, picture caching is force enabled.
Differential Revision: https://phabricator.services.mozilla.com/D51211
--HG--
extra : moz-landing-system : lando
That way CacheIR can still attach an IC and Baseline/Ion don't need to take the
slow path when a TypedArray access happens through a Double not representable as
an Int32.
Differential Revision: https://phabricator.services.mozilla.com/D39045
--HG--
extra : moz-landing-system : lando
That way CacheIR can still attach an IC and Baseline/Ion don't need to take the
slow path when a TypedArray access happens through a Double not representable as
a (positive) Int32.
Differential Revision: https://phabricator.services.mozilla.com/D39044
--HG--
extra : moz-landing-system : lando
Negative int32 and doubles can both be optimised for TypedArray accesses due to
the fact that any number is a canonical numeric index.
With this change any TypedArray access with a double index can be optimised
without regressing bug 1535031 or bug 1526315.
Differential Revision: https://phabricator.services.mozilla.com/D39043
--HG--
extra : moz-landing-system : lando
The definition of canonical numeric index strings means that any access into a TypedArray
with a Double index never reads from the prototype chain. Instead if the Double is not
representable as an Int32, the access is equivalent to an out-of-bounds access. That
means we can substitute any non-Int32 Double index with an arbitrary index which is OOB.
This helps to avoid deoptimising TypedArray accesses with non-Int32 Double values by
handling them as normal out-of-bounds accesses, which are already optimisable.
Differential Revision: https://phabricator.services.mozilla.com/D39041
--HG--
extra : moz-landing-system : lando
The next patch adds code which may fail on OOM, so StringIsTypedArrayIndex's
interface needs to be updated to allow passing on errors.
Differential Revision: https://phabricator.services.mozilla.com/D39037
--HG--
extra : moz-landing-system : lando
Could not reproduce the test fail locally and on tryserver.
Enable the mochitest dom/workers/test/test_multi_sharedWorker.html for fission
Differential Revision: https://phabricator.services.mozilla.com/D51107
--HG--
extra : moz-landing-system : lando
The input operand could change in some cases, resulting in inconsistent return
values from isEffectful and getAliasSet.
Differential Revision: https://phabricator.services.mozilla.com/D51069
--HG--
extra : moz-landing-system : lando