This patch adds the content blocking pref setting for the level 2 list
pref in private windows. Also, we add tests for the new setting in this
patch.
Depends on D165938
Differential Revision: https://phabricator.services.mozilla.com/D165939
Asynchronously opening a connection through the Sqlite module may intersect a
shutdown phase so that the request for the connection happens when the phase is
still open, but the callback is invoked after the phase has been closed.
In this case adding a shutdown blocker to close the connection will fail and
async shutdown is likely to crash after waiting for the Sqlite module.
In these edge cases it's safer to just close the connection and reject to the
consumer.
Differential Revision: https://phabricator.services.mozilla.com/D164597
In `StringBuffer::inflateChars` we now copy the alloc policy from the Latin1 buffer.
This lets us remove the `fc_` and `arenaId_` fields from `StringBuffer`.
Differential Revision: https://phabricator.services.mozilla.com/D165827
Rather than create an array object we can use a vector for these names.
One wrinkle is that since we never mutate the name list after it's attached to
the namespace object we don't need barriers on it. This is more convenient
because it allows us to use the same vector type on the stack in a rooted and
in the object itself. I've added comments that hopefully explain things.
Differential Revision: https://phabricator.services.mozilla.com/D165985
This will allow easier development/changes as we proceed to migrate newtab code to ES modules.
The file was imported from 3fefb99f27/plugin.js
with LICENSE added, and formatted/fixed to ESLint standards.
Differential Revision: https://phabricator.services.mozilla.com/D165819
Automatic update from web-platform-tests
Fixed CI failure of idlharness.js for unexposed overloaded functions. (#37227)
--
wpt-commits: 26372edb32920988006a28ef5149349fcb467c9c
wpt-pr: 37227
Automatic update from web-platform-tests
[shared storage] add permissions policy for individual output gate: selectURL() and privateAggregation
This allows more fine-grained control of the output gates
PR: https://github.com/WICG/shared-storage/pull/52
This CL only implement the PAA check for shared storage part. For FLEDGE, it will be done in a separate CL.
Also add the new features in
kFencedFrameOpaqueAdsDefaultAllowedFeatures: they are supposed to
be used from within the FF.
The private aggregation permissions policy is tested in a browser test / is not easily testable via web_test: right now, only selectURL()’s result rendered in FF can expose state in the worklet; but if the permissions policy is disallowed in the embedder, the FF navigation will fail (as the permissions is in kFencedFrameOpaqueAdsDefaultAllowedFeatures).
Bug: 1400840
Change-Id: I74a285827126f5cf8a43cb780e37693f4c0c7ddf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4105180
Reviewed-by: Liam Brady <lbrady@google.com>
Reviewed-by: Qingxin Wu <qingxinwu@google.com>
Commit-Queue: Yao Xiao <yaoxia@chromium.org>
Reviewed-by: Cammie Smith Barnes <cammie@chromium.org>
Reviewed-by: Alex Turner <alexmt@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1088572}
--
wpt-commits: 672e9117cea01a92608718952f0174b8d490966a
wpt-pr: 37515
Automatic update from web-platform-tests
Fragments may become monolithic even if the node isn't.
So ask the fragment instead of the LayoutBox. This is an old problem,
and it prevented pre-paint from understanding that a monolithic
fragment would be the containing block for OOF descendants (normally in
block fragmentation, OOFs are direct children of a fragmentainer, but
not if they are contained by a monolithic fragment, like in this case).
However, with CL:4110949 the problem became more severe, since we may
now force off fragmentation at the last OOF fragment (if it's inside a
clipped container), making it monolithic.
out-of-flow-in-multicolumn-112.html is a test for the regression, while
out-of-flow-in-multicolumn-113.html is a test that would fail even
without the aforementioned CL.
Bug: 1404718
Change-Id: I68ebd5218c2bd0e3e895eaf757a90cbc8594a028
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4131528
Reviewed-by: Alison Maher <almaher@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1088506}
--
wpt-commits: bd8b3c5448c15c15b7eb67cade1a1913ba07b647
wpt-pr: 37746
Automatic update from web-platform-tests
Restore popover focus no matter if the focus moved during showPopover
See crbug.com/1371629 for context. The prior behavior was to only
return focus on hidePopover() if the focus actually moved while
showing the popover. This CL changes that so that focus always
returns to the previously focused element on hidePopover.
Bug: 1307772
Change-Id: I6614637445f72f171a63df019ed131d20a6a6cca
Fixed: 1371629
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4093435
Auto-Submit: Mason Freed <masonf@chromium.org>
Reviewed-by: Joey Arhar <jarhar@chromium.org>
Commit-Queue: Joey Arhar <jarhar@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1088483}
--
wpt-commits: 4da8c23ccf2e4dc7ac0e50044238e57d2ceb92bb
wpt-pr: 37753