Automatic update from web-platform-tests
[navigation API] Fix flaky scroll restoration test
after-transition-intercept-handler-modifies.html sometimes fails
because the scroll restoration is being overridden if the layout
changes from the previous same document navigation have not yet been
applied. This becomes more consistent when same document navigation IPCs
are prioritized (see crrev.com/c/4981177).
This CL changes the test to ensure rendering happens between the forward
and back navigations, which in turn ensures the new layout and scroll
position were updated before navigating back.
Bug: 1042118
Change-Id: Ia6a3768f8780f9ddaff80f7fd877ddca5c6184b7
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5080962
Commit-Queue: Scott Haseley <shaseley@chromium.org>
Reviewed-by: Nate Chapin <japhet@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1232997}
--
wpt-commits: ff2032f656cec2aa3904e6270925f3fd1306371a
wpt-pr: 43487
Automatic update from web-platform-tests
LoAF: remove desired{Execution|Render}Start
Feedback from the OT was that this attribute is a bit advanced and not
actionable, so removing in favor of keeping the shipped API more nimble.
Bug: 1507960
Change-Id: Ida2fd8b0defbcd1bdb3a12e2ed9b0c5be15ab243
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5078588
Commit-Queue: Noam Rosenthal <nrosenthal@chromium.org>
Reviewed-by: Scott Haseley <shaseley@chromium.org>
Reviewed-by: Michal Mocny <mmocny@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1232876}
--
wpt-commits: b88b515ae656e4d1e5fad72ef2ab196984f515cb
wpt-pr: 43470
Automatic update from web-platform-tests
[soft navigations] Ignore non-attributed LCP before softnav detection
This CL ignores LCPs that are not attributed to the soft navigation
task after a user interaction and before a soft navigation was
detected, as discussed in [1].
It also fixes a bug in soft navigation detection in the case where all
paints arrive before the URL was changed. Currently in such cases, a
soft navigation entry is not emitted. This CL fixes that.
[1] https://github.com/WICG/soft-navigations/issues/29#issuecomment-1831386977
Bug: 1505994
Change-Id: I444ff03c0b64663b913b4e73a7c820b7bab11047
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5071732
Commit-Queue: Yoav Weiss <yoavweiss@chromium.org>
Reviewed-by: Michal Mocny <mmocny@chromium.org>
Reviewed-by: Ian Clelland <iclelland@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1232451}
--
wpt-commits: 143e58acd4ca2f1164359fbb63c7772007ce251c
wpt-pr: 43451
Automatic update from web-platform-tests
Fix handling invalid date for Expires header value "0" as expired
This CL changes handling the invalid Expires header value "0" as a time in the
past and stale, as described in section 5.3 [1] of RFC 9111.
> A cache recipient MUST interpret invalid date formats, especially the value
> "0", as representing a time in the past (i.e., "already expired").
[1] https://www.rfc-editor.org/rfc/rfc9111.html#section-5.3
Bug: 853508
Change-Id: I853b2972c4420936fda8373e292d2d90fdb7988a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4021895
Reviewed-by: Takashi Toyoshima <toyoshim@chromium.org>
Reviewed-by: Hayato Ito <hayato@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Reviewed-by: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1232768}
--
wpt-commits: e8d57f52b64b733a0927503ed31b8e4e9c7100a7
wpt-pr: 42675
Automatic update from web-platform-tests
[WPT] [CSP] Rewrite flaky inline-style-blocked
The test was depending on the order in which the
securitypolicyviolation was being received, and was clearly flaky.
This CL rewrites the test completely.
Bug: 1370215
Change-Id: I829c97a885eefa0cc7a49f0952ea6779e1281a6c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5079209
Reviewed-by: Jonathan Hao <phao@chromium.org>
Auto-Submit: Antonio Sartori <antoniosartori@chromium.org>
Commit-Queue: Jonathan Hao <phao@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1232715}
--
wpt-commits: a83bf9a725f275854b37d31dc1708d08c5dd5670
wpt-pr: 43496
Automatic update from web-platform-tests
compute-pressure: Ensure clean test exit
It can happen on certain bots that the pressure updates are still sent
before disconnect() is processed in the mockPressureService, which can
lead in certain cases to receive more updates than allowed in the test.
This patch adds a `gotPenalty` flag, to make sure that at least one
penalty was applied when reaching the maximum allowed updates.
Change-Id: I535b8c21370d14f13f0d6140d1eb2cc043cbeac2
Bug: 1501324
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5076963
Reviewed-by: Fr <beaufort.francois@gmail.com>
Commit-Queue: Arnaud Mandy <arnaud.mandy@intel.com>
Reviewed-by: Raphael Kubo Da Costa <raphael.kubo.da.costa@intel.com>
Cr-Commit-Position: refs/heads/main@{#1232652}
--
wpt-commits: da0a56526aa23f752fc0186b8cf22fa9f05e2fc8
wpt-pr: 43459
Automatic update from web-platform-tests
Fix progress function calculation
We can simplify the progress function when either all the operands
resolve to the same canonical unit or all the operands have the same type.
Currently `progress(10em from 10em to 100em)` crashes as we try to compute the canonical value in either case of simplification.
This CL changes this behavior to distinguish which simplification path
to use, so that in the mentioned progress() example we just take the
double values when all the operands are of the same type.
Bug: 1503730
Change-Id: I361477ba2a03fd6063861d1d1a82d4b77fa77f2f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5067615
Commit-Queue: Daniil Sakhapov <sakhapov@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1232633}
--
wpt-commits: 94c20e8f17b32ff2adfefd87a1fea07189456be8
wpt-pr: 43391
Automatic update from web-platform-tests
Never break at a resumed parallel block flow inline node.
What I did in CL:5063008 caused trouble, because incoming child break
tokens could be re-propagated twice; once in BoxFragmentBuilder::
AddBreakBeforeChild(), and then again when walking through the
unprocessed incoming inline break tokens in BlockLayoutAlgorithm::
Layout().
Revert the code changes from that CL, and replace it with something
better (and simpler): Never consider breaking before a resumed inline
node in a parallel block flow. This is similar to how we already handle
interleaved block formatting context roots. They may also be interrupted
by floats that got pushed from an earlier fragmentainer, and thus not be
able to resume and place anything in one fragmentainer, and try again in
the next. See e.g. web_tests/external/wpt/css/css-break/float-005.html
Bug: 1506393
Change-Id: If580b5a5f33a8b4ddf86677f79d1a9f06819bc51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5077847
Auto-Submit: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1232515}
--
wpt-commits: cce26e3757dcfd21629f3334072ce9c1292c4d9f
wpt-pr: 43474
Automatic update from web-platform-tests
[wptrunner] Display reruns starting from `1/N` to `N/N` (#43155)
Instead of `0/N` to `(N-1)/N`, which looks incomplete.
--
wpt-commits: dd47ca67f55ac9df45235b2335200fb885dd1357
wpt-pr: 43155
This is expected to be present in ffmpeg, but is only for displaying things on
the command-line, we don't need a "real" implementation.
Differential Revision: https://phabricator.services.mozilla.com/D196062
Running `generate_source_mozbuild.py` needs to be done with a specific version
of pyparsing, this can be done with a virtualenv, like so:
```
cd media/libaom
python3 -m venv temp
. temp/bin/activate
pip install pyparsing==2.4.7
./generate_sources_mozbuild.sh # this runs generate_source_mozbuild.py
```
Differential Revision: https://phabricator.services.mozilla.com/D196060
Ideally we'd check whether we are using mesa, but we have to make the decision before creating the context and need the latter to know whether mesa is involved.
Differential Revision: https://phabricator.services.mozilla.com/D193053
AC_SUBSTs with a lower-case key are not really supposed to be used,
although that has never been enforced, and at least one of them is
used in practice.
At least, that's the theory behind using files to store their value in
config.statusd (added in bug 1402012). Because obviously, on
case-insensitive file systems, a variable that is upper case will use
the same file as the lower case one. If their value is the same, then
fine, but if they aren't, thing go bad.
Until bug 1867457, that held true for TARGET_CPU and target_cpu: their
value was the same. But bug 1867457 changed that. But target_cpu is only
there because it's set by autoconf itself, and we don't care about it.
The result is that the value of target_cpu takes precedence because it's
set last, and overwrites the value of TARGET_CPU in config.statusd,
subsequently making the value read in GenerateAtomicOperations.py wrong.
Differential Revision: https://phabricator.services.mozilla.com/D195959
OffscreenCanvas WebGPU could deliver descriptor of remote texture like other canvases since it uses async ImageContainer(via ImageBridge). Then when CanvasContext::SwapChainPresent() returns valid descritptor of remote texture, the descriptor is delivered correctly to WebRenderImageHost like other canvases with offscreen canvas.
Async wait and callback happen at WebRenderImageHost::UseRemoteTexture() since it uses async ImageContainer(via ImageBridge).
Differential Revision: https://phabricator.services.mozilla.com/D196249
This is a (probably) safe thing to do before going all the way to
removing the file. This will unlock fixing bug 1869078.
Differential Revision: https://phabricator.services.mozilla.com/D196355
It allows multiple edit action preserves `Selection` when updating the DOM tree.
However, most callers do not use `finally` to reset the state, and this makes
edit action handling complicated in some edge cases. Therefore, let's stop
supporting this feature. If Thunderbird requires the feature, the developers
should request additional param for preserving `Selection` like the preceding
patch.
Depends on D196004
Differential Revision: https://phabricator.services.mozilla.com/D196005
