There are some situations that we don't apply storage partitioning, such
as tracker request, privilege reqeusts, and extension requests. In these
case, we don't need to apply CHIPS behavior. Otherwise, we will hit
certain assertions based on partitioning behavior.
In this patch, we also change the way how we determine if a request is
unpartitioned for HTTP requests and tackle an edge cases for extension's
requests.
Differential Revision: https://phabricator.services.mozilla.com/D211506
This patch changes a debug assert, to allow
`nsIDocumentEncoder::OutputFormatFlowed` to be used together with
`::OutputWrap` instead of `::OutputFormatted`.
This change is needed, because `::OutputFormatted` has undesired side
effects, namely converting html tags to plain text tags (for example
`<b>text</b>` to `*text*`).
Differential Revision: https://phabricator.services.mozilla.com/D211674
Automatic update from web-platform-tests
[css-scroll-snap-2] Rename snapchanging to scrollsnapchanging
Per the CSS working group resolution[1], snapchanging should be renamed
to scrollsnapchanging. This patch changes file contents. A follow-up patch
will change file names and directory names.
[1]https://github.com/w3c/csswg-drafts/issues/9697#issuecomment-2089278615
Bug: 40286359, 338290502
Change-Id: If7d5c87a874a32f19f453a6b9ad3f10c167466eb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5538788
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1305040}
--
wpt-commits: 83278a9b8486f07fc6cf27d89f6b4dd292c66bc9
wpt-pr: 46411
Automatic update from web-platform-tests
[text-box-trim] Honor clearance with `<br>`
While `text-box-trim` can trim objects in a line box that
pushes following boxes down, `ClearanceAfterLine()` should be
still valid, because the clearance space isn't part of the
line box. This patch fixes it.
Changes are under a runtime flag enabled only for testing.
Bug: 40254880
Change-Id: Ifc1cdbfbe40adcd69a245c8e0594c41f57bc94b2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5561849
Auto-Submit: Koji Ishii <kojii@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304935}
--
wpt-commits: c1ec59cdb730955e1972d04f7b9621a778118646
wpt-pr: 46452
Automatic update from web-platform-tests
fonts: Remove web fonts when their stylsheet is removed
This is the first part of ensuring that unused fonts do not leak. This
change makes it so that when a stylesheet is removed, the corresponding
web fonts are removed from the `FontContext`.
Note: WebRender assets are still leaked, which was the situation before
for all fonts. A followup change will fix this issue.
Fixes#15139.
Signed-off-by: Martin Robinson <mrobinson@igalia.com>
Co-authored-by: Mukilan Thiyagarajan <mukilan@igalia.com>
--
wpt-commits: 44a942e26bfb2600d6bc158417b3a068c0cc95af
wpt-pr: 46437
Automatic update from web-platform-tests
Reland "webnn: Enforce input data type constraints for gather indices"
This is a reland of commit ef29e11bfb1f1f4eae0935fb58f0e4129620837b
The failure of services_unittests/WebNNGraphImplBackendTest.
BuildAndComputeSingleOperatorGather has been fixed by another CL: https://chromium-review.googlesource.com/c/chromium/src/+/5544945.
This CL adds int32 dataType support check besides uint32 and int64 for
gather indices compared with original CL.
Original change's description:
> webnn: Enforce input data type constraints for gather indices
>
> As specified in https://github.com/webmachinelearning/webnn/pull/646
>
> Bug: 328567884
> Change-Id: I33eba7e1def430b1cb94e3e7a4868e82c5bbd9a3
> Cq-Include-Trybots: luci.chromium.try:mac14-blink-rel,mac14.arm64-blink-rel
> Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5520313
> Reviewed-by: Austin Sullivan <asully@chromium.org>
> Commit-Queue: Lisha Guo <lisha.guo@intel.com>
> Reviewed-by: ningxin hu <ningxin.hu@intel.com>
> Cr-Commit-Position: refs/heads/main@{#1298443}
Bug: 328567884
Change-Id: Ide6a0e1bc6d3ebea7dce6bf37da4318e7b6e1bd1
Cq-Include-Trybots: luci.chromium.try:mac14-blink-rel,mac14.arm64-blink-rel,gpu-fyi-try-win11-qualcomm-rel-64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5532907
Reviewed-by: ningxin hu <ningxin.hu@intel.com>
Commit-Queue: Lisha Guo <lisha.guo@intel.com>
Reviewed-by: Austin Sullivan <asully@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304870}
--
wpt-commits: dde81ead14885761dbf9b0671bcd24a483b12b24
wpt-pr: 46217
Automatic update from web-platform-tests
Use the new "dcb" and "dcz" content encodings of Compressed Dictionary
The spec of Compression Dictionary Transport has been changed to use
new `dcb` and `dcz` content encodings.
https://github.com/httpwg/http-extensions/pull/2784
To follow the spec change, this CL changes the Chromium implementation
and tests as follows:
- Use "dcb" content encoding name instead of "br-d".
- Use "dcz" content encoding name instead of "zstd-d".
- Remove the "Content-Dictionary" response header.
- Check the magic number and the sha256 hash in the head of the
Dictionary-Compressed streams using
SharedDictionaryHeaderCheckerSourceStream.
- Re-generate test files using the new content encodings.
Bug: 1413922
Change-Id: I4f2f40c1f0c3666b4f0b54e34ad966ffccadd96b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5552563
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Reviewed-by: Patrick Meenan <pmeenan@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304826}
--
wpt-commits: 0af64c1077da2f0e27b98cd05e41dc81f28dca3a
wpt-pr: 46436
Automatic update from web-platform-tests
Always have move event listener logic in MoveNodeToNewDocument()
This CL removes the check on moving event listeners from the fast
adoption code, and adds it back to the common path.
Bug: 341104769
Change-Id: Ic9738d9af97fecdcff6c8c45eea0634b6dc3b9dd
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5546684
Reviewed-by: Mason Freed <masonf@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304811}
--
wpt-commits: bb1a8e8eb977ce1ed423668eb23e66978439839a
wpt-pr: 46368
Automatic update from web-platform-tests
[css-scroll-snap-2] Rename snapchanged to scrollsnapchange
Per the CSS working group resolution[1], snapchanged should be
renamed to scrollsnapchange. This patch changes the relevant file
names and directory names.
[1]https://github.com/w3c/csswg-drafts/issues/9697#issuecomment-2089278615
Bug: 40273052, 338290502
Change-Id: I60132f4fe22ed5d5d37902b7f1570f7e96aba401
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5538749
Reviewed-by: Kevin Ellis <kevers@chromium.org>
Commit-Queue: David Awogbemila <awogbemila@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304613}
--
wpt-commits: 99874d7f9d7c393cc0beae06bbc069bb011aa9e6
wpt-pr: 46412
Automatic update from web-platform-tests
Change the input format semantics for TextMetrics::getSelectionRects()
Update how the `end` index works for `getSelectionRects` from being
an inclusive limit on both sides, i.e. [start, end], to being exclusive
for the end limit, i.e. [start, end).
This way, we match the index semantics of the underlying
`Font::SelectionRectForText()` method that is used to calculate the
rects.
Bug: 341213359
Change-Id: I1a09bc256c9f04ae3ae974a587c3e732aa003a74
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5553293
Commit-Queue: Andres Ricardo Perez <andresrperez@chromium.org>
Reviewed-by: Fernando Serboncini <fserb@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304612}
--
wpt-commits: 8fe197f742794a8f6f501b8e976c9f81cd54973c
wpt-pr: 46420
Automatic update from web-platform-tests
[shared storage] Fix some web platform tests
Issue: Some WPTs finish too early and does not actually wait for the
async operations. We encountered test failures due to a mojom
connection CHECK on `CodeCacheHost`, which reveals this underlying
problem.
This patch fixes those cases. Also, for
shared-storage-writable-img-idl-attribute-included-bytes.tentative.https.sub.html,
there are some additional problems:
- The "+" is a special URL character. Thus, we apply
encodeURIComponent on the key/value.
- Passing emoji character directly doesn't seem to work. It's
being translated to a different/unexpected sequence. In this CL,
we replace the emoji with explicit UTF-16 code units created from
String.fromCharCode(). Filed a bug (https://crbug.com/341973427)
for further investigation.
Bug: 341893986
Change-Id: I208e4af410a3a1092a0da88decbe43687fe8b718
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5556543
Reviewed-by: Cammie Smith Barnes <cammie@chromium.org>
Commit-Queue: Yao Xiao <yaoxia@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304604}
--
wpt-commits: 710cfd98ff2cd17106b59df43053ccdd0b370d7b
wpt-pr: 46442
Automatic update from web-platform-tests
[document picture-in-picture] Propagate user activation to the opener
This CL changes browser-process-side user activation logic to allow
activations in document picture-in-picture windows to be used in their
opener windows, and activations in the opener windows to be used in
their document picture-in-picture windows.
This feature is behind an enabled-by-default feature flag.
Specification change:
https://github.com/WICG/document-picture-in-picture/pull/117
Chromestatus: https://chromestatus.com/feature/5185710702460928
Intent to Prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/MwH0ODG4bec
Intent to Ship:
https://groups.google.com/a/chromium.org/g/blink-dev/c/AfzrMoCgccQ
Bug: 331246719
Change-Id: Iedad1e0cb60e04fc1ccf350405f04a399a2b72a1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5393891
Commit-Queue: Tommy Steimel <steimel@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304599}
--
wpt-commits: 58221c60ed5e96327514caffba41f9ad583b20b0
wpt-pr: 45621
Automatic update from web-platform-tests
Fix double-tentative in WPT filename
This somehow got two `.tentative`'s. This removes one of them.
Bug: 335223786
Change-Id: I6bf2b7e9577e586f364784fb6554483110fd8096
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5558172
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: David Baron <dbaron@chromium.org>
Commit-Queue: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304588}
--
wpt-commits: 54d34d6645cf7d256238a8d67a58315f3e75428b
wpt-pr: 46443
Automatic update from web-platform-tests
Fix Null Dereference in css_parsing_utils
This CL addresses a null pointer dereference issue within the
ConsumeColorContrast functions located in css_parsing_utils.cc.
Previously, a null dereference occurred when the code attempted to
retrieve the color provider when the document was null. To resolve
this, the updated code now includes a validation check to ensure the
document object is valid before calling the GetColorProviderForPainting
method.
Bug: 337069153
Change-Id: Ieee6c0e3602b25e8b149c93643e4d55265e4467c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5497219
Reviewed-by: Alison Maher <almaher@microsoft.com>
Commit-Queue: Sam Davis Omekara <samomekarajr@microsoft.com>
Cr-Commit-Position: refs/heads/main@{#1304551}
--
wpt-commits: 3eb175f695ca8064ee616bed9e250595b557a87a
wpt-pr: 46388
Automatic update from web-platform-tests
[anchor] Fix anchor-center crash.
We had a NOTREACHED within grid for anchor-center when it was valid.
Ensure it maps to center.
Bug: 341928664
Change-Id: If9fa88f9febb31333d3d646dfce356cc1456259e
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5552987
Commit-Queue: Mason Freed <masonf@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Auto-Submit: Ian Kilpatrick <ikilpatrick@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304494}
--
wpt-commits: da2dc272ce893b2fcbbc74989c5abdcedb449bd9
wpt-pr: 46415
Automatic update from web-platform-tests
Add back [popover][anchor] CSS rule, behind the flag
The [1] CL removed this, but never added it back (due to how much
work that used to take). Now that @supports blink-feature is a
thing, this puts back the CSS.
[1] https://chromium-review.googlesource.com/c/chromium/src/+/5476428
Bug: 335223786
Change-Id: Idc37e3c5f783259bda3bcb73e1e427233000c46c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5555622
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304493}
--
wpt-commits: 323d73b2120883e99b71df574ac439c12a8fc33a
wpt-pr: 46410
Automatic update from web-platform-tests
[text-box-trim] Support invalidations
This patch adds the layout invalidations for the
`text-box-trim` and the `text-box-edge` properties.
Changes are under a runtime flag enabled only for testing.
Bug: 40254880
Change-Id: I56f1d1f0a7e9c6667937c90e94d7dfa91615771a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5552565
Reviewed-by: Lingqi Chi <lingqi@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Auto-Submit: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304491}
--
wpt-commits: fbffd1d2a410c06bcf81fd488240b842526f71e7
wpt-pr: 46440
Automatic update from web-platform-tests
Correct implementation of calc-size() interpolation rules.
I believe I initially implemented these before the spec was written (or
before I was aware that it was). This updates the interpolation rules
to follow https://drafts.csswg.org/css-values-5/#interp-calc-size plus
the clarifications in https://github.com/w3c/csswg-drafts/issues/10220 .
This doesn't implement the IACVT (invalid at computed value time) aspect
of the clarification in https://github.com/w3c/csswg-drafts/issues/10220
and therefore adds both TODO comments and failing tests. (The tests are
useful to check for lack of crashes; when I first wrote them they did
crash and I needed to fix the crashes.)
Bug: 313072
Change-Id: Ia9903bd138c3afb58ef12da45171920d28de8fa6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5546294
Commit-Queue: David Baron <dbaron@chromium.org>
Reviewed-by: Daniil Sakhapov <sakhapov@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304382}
--
wpt-commits: 5d96f029e638e780bac314057ee680a0fe76ecde
wpt-pr: 46413
Automatic update from web-platform-tests
Remove experimental oversized-images policy.
This document policy (previously feature policy) has been in an
experimental state for several years, and there are no current plans to
ship it. Removing the feature to reduce the maintenance burden of unused
code.
Bug: 340920459
Change-Id: I3a2f51c08e65861cc66adcfc90382b4929dd175b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5544840
Commit-Queue: Ian Clelland <iclelland@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304366}
--
wpt-commits: b72469e9736094b6972319fb39a583ee443262a3
wpt-pr: 46322
Automatic update from web-platform-tests
[WebDriver BiDi] fix `test_release_mouse_sequence_resets_dblclick_state` (#46310)
* Move test to tentative, as the expected behavior is not clear yet.
* Remove parameter, as the double click is tested in [`test_dblclick_at_coordinates`](077700f985/webdriver/tests/bidi/input/perform_actions/pointer_mouse_multiclick.py (L66C35-L66C43)).
--
wpt-commits: fe6ef3a2fa1fa9c1bf18ffd174f69b391e1be4b3
wpt-pr: 46310
Automatic update from web-platform-tests
[text-box-trim] Test block-end with Ruby
This patch adds a test of the `text-box-trim` property for the
block-end behavior when a Ruby hangs to the block-end side.
The test and reference for the block-start added in
crrev.com/c/5539108 are updated to share the reference file.
Bug: 40254880
Change-Id: Ie068940eff74aab2eb4baa7588b37baaef59c590
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5553008
Commit-Queue: Koji Ishii <kojii@chromium.org>
Auto-Submit: Koji Ishii <kojii@chromium.org>
Commit-Queue: Lingqi Chi <lingqi@chromium.org>
Reviewed-by: Lingqi Chi <lingqi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304323}
--
wpt-commits: e7a9f83c6176839320eb67e4423599bf29d4492a
wpt-pr: 46431
Automatic update from web-platform-tests
[text-box-trim] Test block-end with initial-letter
This patch adds a test of the `text-box-trim` property for the
block-end behavior when an initial-letter hangs to the
block-end side.
The block-start side test was added at crrev.com/c/5540990.
Bug: 40254880
Change-Id: I6c71de66106aa3accf092c39b5b2717faf972f22
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5552564
Commit-Queue: Lingqi Chi <lingqi@chromium.org>
Reviewed-by: Lingqi Chi <lingqi@chromium.org>
Auto-Submit: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304320}
--
wpt-commits: 0e122283465030b319a805fa77c52a8f9ee3eb55
wpt-pr: 46430
Automatic update from web-platform-tests
Fix a DCHECK if a block was seen in font-feature-settings.
We cannot Consume() in the streaming parser without first checking that
there's no block involved.
Fixed: 341349803
Change-Id: I0740fe7359f056a561dd1a82f1355b999537945a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5554250
Commit-Queue: Steinar H Gunderson <sesse@chromium.org>
Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304312}
--
wpt-commits: affa7c34cd21e11106e768ce8ff487679deee6cd
wpt-pr: 46399
Automatic update from web-platform-tests
[text-box-trim] Test block-end accumulations
This patch updates a test for when the element to trim has
different `text-box-edge` value from the `text-box-edge` value
of the element that has `text-box-trim`, the same condition as
crrev.com/c/5547563, but for block-end side.
Bug: 40254880
Change-Id: Ibaaadee9ef41319c78921b116ca2daae340c3492
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5553822
Auto-Submit: Koji Ishii <kojii@chromium.org>
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Kent Tamura <tkent@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1304304}
--
wpt-commits: 16e779dd4b54b9dc240084cea510132ae698efc7
wpt-pr: 46427