In bug 1864392, the urgency parameter set in our HTTP requests [1] is
adjusted according to the value of the internal priority. This patch
adds basic tests to verify some adjustments, and indirectly the internal
priority, for scripts, images, styles, fonts and global fetches using
different values of fetchpriority.
This is done by introducing a Python handler [2] that serves different
kind of content depending on the urgency parameter it receives and a
WPT test that extracts the urgency from the served content.
[1] https://www.rfc-editor.org/rfc/rfc9218.html#name-urgency
[2] https://web-platform-tests.org/writing-tests/python-handlers/index.html
Differential Revision: https://phabricator.services.mozilla.com/D211988
Technically, screenshots/customScreenshotURLs are still forwardable to callers by
way of retrieving frecent and pinned sites via NewTabUtils.
Differential Revision: https://phabricator.services.mozilla.com/D212568
In DesktopCapture, the callback OnCaptureResult also returns a result of
CaptureFrame, whether it was successful or failed. When ERROR_PERMANENT
is returned, it means that all the following attempts to capture a frame
will not succeed and at this point we should stop capturing. To stop
capturing, we propagate CaptureEnded event up to the DeviceListener and
stop screencast.
Differential Revision: https://phabricator.services.mozilla.com/D201956
Due to it's near end of current cycle, let's enable this new event only in
the Nightly channel. Then, let's make it ride the train starting from the
next cycle.
Differential Revision: https://phabricator.services.mozilla.com/D206332
This adds the command `mach repackage snap`, which packages the current
build as a Snap (with the app name firefox_devel, to not interfere with
installs of the normal firefox package). It can also accept a tar file
as input, for example to repack a build from Taskcluster.
It also adds `mach repackage snap-install`, which installs the package
and connects its plugs with `snap connect` (normally done by default,
but not for an unsigned package like this).
Building a Snap package requires the `snapcraft` command, which is
available as a Snap (and maybe from other package managers).
Depends on D182615
Differential Revision: https://phabricator.services.mozilla.com/D182616
The `mach repackage snap` command creates a Snap named `firefox-devel`
(currently only Firefox is supported), in order not to interfere with
the official package. We ignore the `SNAP_NAME` env var if it names
a different app (assuming it was an unconfined Snap that launched a
non-Snap Firefox as a helper), so we need to recognize our own name with
the "-devel" suffix to avoid potential odd behavior (see bug 1825181 for
an example).
Differential Revision: https://phabricator.services.mozilla.com/D182614
Automatic update from web-platform-tests
[text-box-trim] Fix end for block-in-inline
This patch fixes trimming the end for block-in-inline.
All changes are under a runtime flag enabled only for testing.
Bug: 40254880
Change-Id: Id711aa3f28b458a9594ba659b308a03cb381de1d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5588017
Commit-Queue: Lingqi Chi <lingqi@chromium.org>
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@{#1309228}
--
wpt-commits: 30374552aeb865ab70f691844aedd6534657f37c
wpt-pr: 46585
Automatic update from web-platform-tests
[text-box-trim] Fix two block-in-inline in a row
When the first formatted line is inside of a block-in-inline,
`IsBlockStartTrimmed` needs to be propagated from the block.
When normal inline follows, the propagation isn't necessary
because the algorithm checks `IsFirstFormattedLine()`, but the
issue appears when a block-in-inline follows it. The test for
followed by normal inline is in:
`text-box-trim-block-in-inline-start-001`.
Tests for end will be in following patches.
All changes are under a runtime flag enabled only for testing.
Bug: 40254880
Change-Id: I5f053d5999d98378ef4b39cacec2d6923aa1d8c6
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5591191
Reviewed-by: Lingqi Chi <lingqi@chromium.org>
Auto-Submit: Koji Ishii <kojii@chromium.org>
Commit-Queue: Lingqi Chi <lingqi@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1309185}
--
wpt-commits: edf44fecb0e82a320eb94acaed95189ec80ab87c
wpt-pr: 46582
