The inclusions were removed with the following very crude script and the
resulting breakage was fixed up by hand. The manual fixups did either
revert the changes done by the script, replace a generic header with a more
specific one or replace a header with a forward declaration.
find . -name "*.idl" | grep -v web-platform | grep -v third_party | while read path; do
interfaces=$(grep "^\(class\|interface\).*:.*" "$path" | cut -d' ' -f2)
if [ -n "$interfaces" ]; then
if [[ "$interfaces" == *$'\n'* ]]; then
regexp="\("
for i in $interfaces; do regexp="$regexp$i\|"; done
regexp="${regexp%%\\\|}\)"
else
regexp="$interfaces"
fi
interface=$(basename "$path")
rg -l "#include.*${interface%%.idl}.h" . | while read path2; do
hits=$(grep -v "#include.*${interface%%.idl}.h" "$path2" | grep -c "$regexp" )
if [ $hits -eq 0 ]; then
echo "Removing ${interface} from ${path2}"
grep -v "#include.*${interface%%.idl}.h" "$path2" > "$path2".tmp
mv -f "$path2".tmp "$path2"
fi
done
fi
done
Differential Revision: https://phabricator.services.mozilla.com/D55442
--HG--
extra : moz-landing-system : lando
Changes the existing fast-path for 2^n to any (2^m)^n. And adds a fast-path for
uint64 BigInts, so we only need to allocate a single BigInt when the result also
fits in uint64.
The for-loop was changed to a while-loop, because that made it easier to give
both loops the same structure.
Differential Revision: https://phabricator.services.mozilla.com/D54770
--HG--
extra : moz-landing-system : lando
While waiting for "timeupdate" for a currentTime >0 playback could end before
we're done waiting. This causes both unexpected test failures and a timeout.
The simplest way out of this seems to be to first wait for the play promise to
resolve so we know the output tracks are available; second to set currentTime to
0 even if it already is 0. By spec this still seeks, so it is fine.
Differential Revision: https://phabricator.services.mozilla.com/D54632
--HG--
extra : moz-landing-system : lando
The recent addition of the JSOP_NEWOBJECT_WITHGROUP opcode for bug
1598347 (itself a regression fix for 1580246) has led to an issue when
more than a certain number of array elements with the same group are
created within an array literal. In particular, when too many objects
are created, the preliminary-objects-set for the ObjectGroup becomes
full and hits a MOZ_CRASH. This patch avoids trying to add to the
preliminary object set in the _WITHGROUP case.
Differential Revision: https://phabricator.services.mozilla.com/D55736
--HG--
extra : moz-landing-system : lando
Some of these were obvious typos. Others probably reflect once-correct components
that have been combined, split, or otherwise obsoleted; for these I've tried to
use the component associated with the bugs for recent changes to the affected files.
Differential Revision: https://phabricator.services.mozilla.com/D55756
--HG--
extra : moz-landing-system : lando
* Removed the STATUS_LINK constant.
* Removed the statusType parameter from nsIWebBrowserChrome::setStatus.
* Removed the setStatusWithContext method. No one uses the information from
statusContext.
* Removed the nsIWebBrowserChrome2 interface as setStatusWithContext was the
only method.
Differential Revision: https://phabricator.services.mozilla.com/D55195
--HG--
extra : moz-landing-system : lando
Depends on D55204
This is just a smoke test to verify that the HAR file is created.
We should probably expand this and test the content as well, but we can handle that in follow up bugs
Differential Revision: https://phabricator.services.mozilla.com/D55271
--HG--
extra : moz-landing-system : lando
This fixes several gaps:
- event api changes
- networkEvent no longer emitted by debugger client
- shape of expected HAR items changed
- use the connector from the netmon api
This is the minimum set of changes I could do to get HAR automation to save valid HAR files again.
Differential Revision: https://phabricator.services.mozilla.com/D55204
--HG--
extra : moz-landing-system : lando
Automatic update from web-platform-tests
Cookie Store: Refactor tests to also work in window context.
This refactor condenses service worker test files by converting the
service worker scripts into .any.js WPT files that test both window and
worker contexts.
Change-Id: Iee64f5cc68b939ab02b06910444b8ebffdf359a4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1851232
Commit-Queue: Victor Costan <pwnall@chromium.org>
Reviewed-by: Victor Costan <pwnall@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720381}
--
wpt-commits: ff11f93316527e37ec580adca01a9cf0a58a297e
wpt-pr: 20468
Automatic update from web-platform-tests
Delete invalid test. (#20547)
It seems it expects `transform: rotate(1deg, 20px, 20px)` to somehow be valid.
It was introduced in cdc3032f56c86cc68121e54e169485441d9cdb1a, pointing to https://www.w3.org/TR/css-transforms-1/#svg-transform-functions, which doesn't say anything like that.
Doesn't pass in any browser.
--
wpt-commits: 5df56b25e1cb81f81fe16c88be839f9fd538b41e
wpt-pr: 20547
Automatic update from web-platform-tests
Fix parser mXSS sanitizer bypass for <p> and <br> within foreign context
Prior to this CL, the following code:
<svg></p></svg>
parsed to this innerHTML: <svg><p></p></svg>
This is in contrast to this code:
<svg><p></svg>
which parses to <svg></svg><p></p>
The fact that the </p> is left inside the <svg> allowed sanitizer
bypasses as detailed in [1]. Please also see [2] for the spec
discussion.
With this CL, </p> and </br> within a foreign context now cause
the closing of the foreign context.
[1] https://research.securitum.com/dompurify-bypass-using-mxss/
[2] https://github.com/whatwg/html/issues/5113
Bug: 1005713
Change-Id: Ic07ee50de4eb1ef19b73a075bd83785c99f4f891
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940722
Reviewed-by: Kouhei Ueno <kouhei@chromium.org>
Commit-Queue: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720315}
--
wpt-commits: 561b765308e6d188618f3ba73091bb598d8357ce
wpt-pr: 20489
Automatic update from web-platform-tests
Portals: Do not create a RemoteFrame for a portal when a portal if
inserted into a disconnected node.
Bug: 1029508
Change-Id: I8d90a488198b0772baa2bd41a16c6a330fc792fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943310
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: Lucas Gadani <lfg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720283}
--
wpt-commits: 20bb1ca5db519ee5d37ece6492868f8a6b65a2e7
wpt-pr: 20536
Automatic update from web-platform-tests
Add ref tests for web-animation play controls
This patch adds ref tests for play controls and enables these tests to
run as part of a virtual test suite with the compositor enabled. The
tests are designed to catch regression that break animation play
controls.
Tests were added for syncing the compositor start time as well as
updating the playback rate.
The test for zero playback rate exposed a bug where it should have been
disabled on the compositor but wasn't. This bug is also fixed in the
patch.
Bug: 1029123
Change-Id: I0304d80b93ef273dd2f1dbcd58e2371bc046941e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1943367
Reviewed-by: Robert Flack <flackr@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720190}
--
wpt-commits: 995900fc628dcbfd79fb78dc816e5bea17119c84
wpt-pr: 20541
Automatic update from web-platform-tests
Fix play controls for composited animations. (#20492)
Play controls recently broke for composited animations due to timing
differences on when variables are changes. Per spec, the start time is
not cleared when pausing an animation until after the animation is
ready. This discrepancy lead to a case when PreCommit would not get
called when pausing a composited animation.
Reverse and updatePlaybackRate were also broken for composited
animations. We cannot composite infinite duration animations in the
reverse direction. We were using playback rate instead of
EffectivePlaybackRate in one of our checks for compositor eligibility,
and falling to catch this case.
Finally, with changes to when start time is cleared, we can be in a
case where it is important to preserve the start time or the current
time when starting a composited animation. Fortunately, we can
determine when start time is the important factor based in whether the
animation is pending.
Next step: Add WPT tests that would have caught the regressions. Filed
as issue 1029123.
Bug: 1028985, 1028986
Change-Id: I4edf851790a860d20962df84944558e7dbc1863a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1940885
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720042}
--
wpt-commits: dfcdaf109407d4b8db06e8fbf37b2a0cb80f251f
wpt-pr: 20492
Automatic update from web-platform-tests
Remove cross fade from backgrounds
background-image-interpolation should not use cross fade. Bug filed: https://bugs.chromium.org/p/chromium/issues/detail?id=1029358
background-image-interpolation when interpolate from single image to multiple images at progress -0.3 will give from, from instead just from.
Bug filed: https://bugs.chromium.org/p/chromium/issues/detail?id=1029529
Bug: 900581
Change-Id: I481725439b8ef3944693b4c65dbc4112eca42265
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1942492
Reviewed-by: Xida Chen <xidachen@chromium.org>
Commit-Queue: Hao Sheng <haozhes@chromium.org>
Cr-Commit-Position: refs/heads/master@{#720267}
--
wpt-commits: c2efb44a06853e1acaf0f2cbc298399bdee28a32
wpt-pr: 20514
