This patch:
- adds a new pref for site quota.
- sets 25 MB as the default site qutoa.
- renames LocalStorageManager::GetQuota() to LocalStorageManager::GetOriginQuota().
- adds LocalStorageManager::GetSiteQuota().
- updates LocalStorage quota tests.
Differential Revision: https://phabricator.services.mozilla.com/D101756
During selfhosting initialization, we perform a GC and then freeze the
global. This means we must clear any dangling references before this GC
happens. This fixes a recent regression where we started keeping the
top-level script alive unintentionally. Also ensure the options mark the
script as run-once to match that old behaviour.
Differential Revision: https://phabricator.services.mozilla.com/D101637
This patch makes it so that any retrigger actions being performed from Treeherder on browsertime tasks (through add-new-jobs, retrigger, and retrigger-multiple) will always retrigger the vismet (visual-metrics) tasks correctly. Furthermore, when a vismet task is retriggered, we'll retrigger the browsertime test task.
Differential Revision: https://phabricator.services.mozilla.com/D101404
As is the case with GTK, Android provides an OS override to display times in
AM/PM or 24 hour format. This moves the code for rewriting skeletons from the
GTK specific code to OSPreferences, and calls it from the Android OSPreferences
implementation.
This was tested manually by visiting the file:/// uri. I don't believe this is
feasible to test from automation, as it would require changing Android OS settings
from within our test code.
Differential Revision: https://phabricator.services.mozilla.com/D101641
Automatic update from web-platform-tests
usb: Add a manual test for USB transfer completion order
This manual test attempts to reproduce a case seen in issue 1153647
where parallel calls to transferIn(), recommended for performance, can
return data out of order.
This test is a starting point in the investigation as it only sends a
small amount of data while the original report involves much larger
transfers.
Bug: 1153647
Change-Id: I4f4b8f5ad502d08ae7c4fb9cc22889047029afc4
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2587950
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Reviewed-by: James Hollyer <jameshollyer@chromium.org>
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841773}
--
wpt-commits: 28ac8ff82f255bfb5c799b6d433d19d0a0eb0e34
wpt-pr: 26873
Automatic update from web-platform-tests
[LayoutNG] Fix OOF not painted in "tall" multicolumns
In some cases as the one described in https://crbug.com/1151383,
non-fragmented OOF are not painted. The computed |offset_from_root|
seems to be invalid and this CL fixes it.
Bug: 1151383
Change-Id: Ib85440577442782a1f09f704d2224214d4822232
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2607670
Commit-Queue: Benjamin Beaudry <benjamin.beaudry@microsoft.com>
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841740}
--
wpt-commits: 1affd0458528e1ccde884f4e4c942da7d056856b
wpt-pr: 27019
Automatic update from web-platform-tests
fix: relax performance API checks for prefetch test
This test was flaky because occasionally one or more paint events
were included in the Performance API data. The check's been
relaxed to remove the intermittent failure.
Bug: 901056, 1164166, 1160655
Change-Id: I1fc89ad1cd60bd326b1516ae6b93814f10922b30
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618483
Commit-Queue: Richard Townsend <richard.townsend@arm.com>
Reviewed-by: Mason Freed <masonfreed@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841696}
--
wpt-commits: 2491f9dbc12e38e742b7a28395bacf42cd689368
wpt-pr: 27114
Automatic update from web-platform-tests
Remove port 554 from the restricted list
Blocking port 554 has known compatibility issues. Unblock it.
BUG=1148309,1164418
Change-Id: I51de0e944cdd57cad5f2d5fec145dad7320dfc51
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2618418
Auto-Submit: Adam Rice <ricea@chromium.org>
Reviewed-by: Matt Menke <mmenke@chromium.org>
Commit-Queue: Matt Menke <mmenke@chromium.org>
Commit-Queue: Adam Rice <ricea@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841622}
--
wpt-commits: f67cae457639f098da3b09992d7c88a46147fee8
wpt-pr: 27112
Automatic update from web-platform-tests
Fix reftest-wait usage in some tests
--
Add a lint that anything that uses the reftest-wait script specifies reftest-wait
Not having the reftest-wait class on the root is a pretty clear indication of a bug
and one that's relatively easy to avoid. Of course this doesn't catch all cases where
something happens after load and reftest-wait is required but it at least catches some
of the more obvious errors
--
Fix mypy annotations for parsing
--
Update tools/lint/rules.py
Co-authored-by: Chris Harrelson <chrishtr@gmail.com>
--
wpt-commits: 7bf1d81fca9dfa5a5bcc33ab4e2c5b6219426a11, 5b4049b18faae5953d3b8470715bb405ea99eec4, c913981fd467faca7de998a269afa1f8e8961bec, 67c3f228ec036e90aeb11d2ce13c0bb8061584d3
wpt-pr: 27075
Automatic update from web-platform-tests
[css-flex] Apply transferred min/max sizes to svg with no natural sizes
When deriving flex base size of an svg that has an aspect ratio but no
natural height or width, we were ignoring min/max sizes specified in the
cross-axis direction, even though they should transfer through the
aspect ratio and restrict the stretch fit into the available size.
Bug: 1162704
Change-Id: If502de43a876e41e6f3784aea089edcd2467ba60
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2614470
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841586}
--
wpt-commits: d81b71f027dc76082e8a77370d8a6642666cfca9
wpt-pr: 27091
Automatic update from web-platform-tests
WebSocketStream: Make backpressure-receive.any.js work again
The web test
external/wpt/websockets/stream/tentative/backpressure-receive.any.js
started failing on Windows 10 with the switch to Python 3. It appears
some additional buffering is happening in the OS. As a workaround,
split the large message that is supposed to be delayed by backpressure
into 16 parts.
BUG=1155106
Change-Id: Ifa2b04e4857f3c537721735cec187f610c053d99
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2613853
Commit-Queue: Domenic Denicola <domenic@chromium.org>
Auto-Submit: Adam Rice <ricea@chromium.org>
Reviewed-by: Domenic Denicola <domenic@chromium.org>
Cr-Commit-Position: refs/heads/master@{#841571}
--
wpt-commits: 4f82b31b95639c3d57d7b99ca56f0f03bb6ec507
wpt-pr: 27109
Automatic update from web-platform-tests
Fixing runner when autorun flag is true
- The tests on complete callback was not being registered
--
wpt-commits: a351e924c5548601a65ed3f1ff6d7b68747766da
wpt-pr: 27073
This uses SkDraw::ComputeResScaleForStroking to ensure we exactly match the resolution scale
that is chosen for drawing the stroked path inside the guts of Skia. This should ensure these
two don't get out of sync.
This also cleans out the old overscale code in ComputeResScaleForStroking that was necessary
during an ancient Skia porting effort but has now bitrotted into irrelevance.
Differential Revision: https://phabricator.services.mozilla.com/D101686
Syncing the container FeaturePolicy across BrowsingContext is actually
a bit more heavy-handed than necessary. We only ever need a container
FeaturePolicy when inheriting a FeaturePolicy in exactly the document
the container contains. Not every process that the tree the container
is a part of. So instead of storing a FeaturePolicy in a synced field,
we manually send it to the correct WindowGlobalChild (which
corresponds to a document) and retrieve it from there.
Differential Revision: https://phabricator.services.mozilla.com/D61479
