This patch enables PSM and Firefox to use TLS 1.3 Encrypted Client Hello (draft -08). Specifically:
- Compile NSS with NSS_ENABLE_DRAFT_HPKE=1
- Add ECH "public_name" handling in SSLServerCertVerification.cpp (see: https://tools.ietf.org/html/draft-ietf-tls-esni-08#section-6.3.2)
- Adds `mIsAcceptedEch` to TransportSecurityInfo, and xpcshell tests for ECH use cases
- Adds EncryptedClientHelloServer to facilitate the xpcshell tests
- Un-ifdef Set/GetEchConfigs code in nsNSSIOLayer.cpp. Also reverted the Base64 encoding and decoding, as the data returned from DNS is already decoded (wire-format).
Differential Revision: https://phabricator.services.mozilla.com/D92651
Automatic update from web-platform-tests
Support 'disclosure-open' and 'disclosure-closed' for 'list-style-type'
property
* core/css, core/style, web_tests/external/wpt:
Changes to recognize new keywords 'disclosure-open' and
'disclosure-closed'.
* layout/layout_details_marker.*,
layout/layout_tree_as_text.cc,
paint/details_marker_painter.*:
Changes to make DetailsMarkerPainter::GetCanonicalPath() static in
order to share it with ListMarkerPainter.
These files has no behavior changes.
* paint/list_marker_painter.cc:
Calls DetailsMarkerPainter::GetCanonicalPath() to get a Path, and draw
it on |context|.
* layout/list_marker.cc:
Adjust the layout size for 'disclosure-*'.
The size of 'circle', 'disc', 'square' is "ascent * 1 / 3", and it's
too small for 'disclosure-*'. We apply "font_height * 2 / 3" instead,
and it's same as the default size of ::-webkit-details-marker.
* layout/list_marker_text.cc, wtf/text/character_names.h:
Add text representations of 'disclosure-open' and 'disclosure-closed'.
This CL adds a simple rendering test. A following CL will add more
coverage.
I2S: https://t.co/1a7z357RV9
Bug: 590014
Change-Id: I1acad5a102c7cfcc91101fca283fde32fefae06f
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567548
Commit-Queue: Kent Tamura <tkent@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833566}
--
wpt-commits: 92a7e0486f73461372fe6b93009f16f5ab6cfe29
wpt-pr: 26732
Automatic update from web-platform-tests
serial: Export manual tests into Web Platform Tests
These tests don't have any automation dependencies (since they are
manual) so can be exported first.
Bug: 884928
Change-Id: I6a3b9240d7ce8d61bfea43e5445d1334725bbd64
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2572745
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Commit-Queue: Joshua Bell <jsbell@chromium.org>
Auto-Submit: Reilly Grant <reillyg@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833542}
--
wpt-commits: 1cc8547873324c7b70ab00e5d2f7d6d0b0b59774
wpt-pr: 26752
Automatic update from web-platform-tests
Simulate user inputs in css/selectors/focus-visible-004.html
Use testdriver Action API to simulate mouse click actions in
css/selectors/focus-visible-004.html.
Bug: 1145677
Change-Id: I3715e32893f0e977226412d8ffc8b6928ff7a1a5
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2551803
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833520}
--
wpt-commits: 733dbcfd53c36c69104b24b27b3cc44e09b6a3fa
wpt-pr: 26626
Automatic update from web-platform-tests
Simulate user inputs in pointerevent_capture_suppressing_mouse.html
Use testdriver Action API to simulate mouse actions in
pointerevents/pointerevent_capture_suppressing_mouse.html.
Bug: 1145677
Change-Id: I329d4b814020dd3c0d22c807c36828f5e868b4cf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568825
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833510}
--
wpt-commits: 88780a69aa6ef42becab170fc1ddec9e5a61704e
wpt-pr: 26724
Automatic update from web-platform-tests
usb: Support composite devices using the WinUSB driver
This adds support for an uncommon configuration in which a composite USB
device has the WinUSB driver loaded for the whole device rather than
using Microsoft's composite driver to create device nodes for each
device function.
A manual test which confirms that all calls to claimInterface() succeed
or fail in a reasonable time has been added.
Bug: 1150758
Change-Id: If86d2e21dbc575cadea943a9c319029a10c78b36
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568546
Reviewed-by: Matt Reynolds <mattreynolds@chromium.org>
Commit-Queue: Reilly Grant <reillyg@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833505}
--
wpt-commits: 7f680aee5f41278be2b4146b7669b5cc8caec47f
wpt-pr: 26713
Automatic update from web-platform-tests
Simulate user inputs in css/selectors/focus-visible-003.html
Use testdriver Action API to simulate mouse click actions in
css/selectors/focus-visible-003.html.
Bug: 1145677
Change-Id: I18d3862d524c0a917c056891e7012c589b8252e2
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2548197
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833502}
--
wpt-commits: c7c5d9402225a17a0c13d58747d4d0088b299d46
wpt-pr: 26624
Automatic update from web-platform-tests
Test closing multiple datachannels
Tests that when a PeerConnection closes, all open datachannels
get the error and close events.
(The bug was fixed earlier, but this adds a test for it)
Bug: webrtc:6881
Change-Id: I4734f3d29333dcad98c34cf5dbdc8d4b04a5f986
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568278
Commit-Queue: Harald Alvestrand <hta@chromium.org>
Reviewed-by: Henrik Boström <hbos@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833346}
--
wpt-commits: dc60fe2cbd1292bb2166feba1f24971969e26154
wpt-pr: 26716
Automatic update from web-platform-tests
[CORS-RFC1918] Adding WPT tests for fetch in insecure contexts.
Adds tests verifying that fetch takes into account the CORS-RFC1918
restrictions regarding secure contexts.
These tests are ran with the CORS-RFC1918 flag as a virtual suite
because the flag currently breaks other non related tests due to
inheritance rules not being implemented.
Bug: 1138907
Change-Id: I0b5241c0ed13b4b6247310f19fdd0889351ee54b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2517593
Commit-Queue: Arthur Hemery <ahemery@chromium.org>
Reviewed-by: Titouan Rigoudy <titouan@chromium.org>
Reviewed-by: Arthur Sonzogni <arthursonzogni@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833313}
--
wpt-commits: 9533c723edd37e31e092edcb6bbf29c636d2f087
wpt-pr: 26575
Automatic update from web-platform-tests
DOM: signal support for addEventListener()
Tests for https://github.com/whatwg/dom/pull/919.
--
wpt-commits: 625e1310ce19e9dde25b01f9eda0452c6ec274da
wpt-pr: 26472
Automatic update from web-platform-tests
Simulate user inputs in input-events/input-events-get-target-ranges.html
Use testdriver Action API to simulate key actions in
input-events/input-events-get-target-ranges.html Added . We have to
disable it because we do not support key actions in gpuBenchmarking
when running the tests in our chromium bots.
Bug: 1145677
Change-Id: I5176f374aaa79d771a78ef651f63098f039101da
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2533965
Commit-Queue: Lan Wei <lanwei@chromium.org>
Reviewed-by: Mustaq Ahmed <mustaq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833135}
--
wpt-commits: 4ac59dc8fb85817b4cf8fc801b524ed74743d2c1
wpt-pr: 26514
Automatic update from web-platform-tests
FontAccess: Fail concurrent font chooser requests
This changes the behavior from concurrent font chooser requests all
returning the same data from a single chooser invocation to failing a
subsequent request.
As implemented, the User Activation check will consume the activation,
failing any other in-flight requests.
Fixed: 1149621
Change-Id: If14e7e12ff52967e8dc49c383a66da94995c9134
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568931
Commit-Queue: Olivier Yiptong <oyiptong@chromium.org>
Auto-Submit: Olivier Yiptong <oyiptong@chromium.org>
Reviewed-by: Joshua Bell <jsbell@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833129}
--
wpt-commits: 6053b17de25520801d0534efbf3f7d200104ece0
wpt-pr: 26727
Automatic update from web-platform-tests
Make <meta name=referrer content=default> use the default referrer policy
The HTML meta tag allows one to set a document's referrer policy by
providing values to
<meta rel=referrer content={referrer policy here}>
In addition to all of the referrer policy identifiers (unsafe-url,
no-referrer-when-downgrade, etc), the HTML spec allows a few legacy
values for the "content" attribute:
"never" is treated as if it instead read "no-referrer",
"always" as "unsafe-url",
"origin-when-crossorigin" as "origin-when-cross-origin", and
"default" as "no-referrer-when-downgrade".
This CL incorporates a behavior change proposed in a new spec pull
request https://github.com/whatwg/html/pull/5783, which updates the
"default" meta tag keyword to, instead of being statically mapped to
no-referrer-when-downgrade", cross-reference the actual default policy
value.
It also adds test coverage for all of the legacy keywords by adding new
test cases to wpt/referrer-policy/spec.src.json; the referrer policy
WPTs didn't previously cover this behavior.
Additionally, the CL removes a few now-redundant Blink web tests
covering the behavior that WPTs now verify.
This change is web-visible, but I think it's arguably covered by the
recently shipped change updating the default referrer policy from its
previous value of no-referrer-when-downgrade to a new value of
strict-origin-when-cross-origin. [1] At the time the <meta> behavior was
originally written into the spec, there wasn't an explicit single source
of truth for the "default referrer policy" per se: instead, specs
(Fetch, HTML, and the WebAppSec Referrer Policy spec) individually
defined fallback behavior in "no policy specified" cases by referring
specifically to the "no-referrer-when-downgrade" policy value.
[1]: https://groups.google.com/a/chromium.org/g/blink-dev/c/lqFuqwZDDR8/m/nKPRTc7DAQAJ
Fixed: 1154350
Change-Id: Ifb3bf9aa9f773c64af1a6e79f39511cf1c1bd8fa
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567977
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Commit-Queue: David Van Cleve <davidvc@chromium.org>
Cr-Commit-Position: refs/heads/master@{#833114}
--
wpt-commits: 260262e3293459fed0f73c430100706abdc32a45
wpt-pr: 26710
Automatic update from web-platform-tests
Avoid problem of decomposited effect on SVG root
This CL avoids the problem by
- Disabling compositing of SVG child for will-change:top etc. which
don't apply.
- Including CompositingReason::kSVGRoot on the effect node (if exists)
on SVG root to prevent the effect node from being decomposited during
PaintArtifactCompositor::Update(), to ensure the composited layer for
SVG root will create a render surface when needed. We still need to
create a better solution for this (tracked by crbug.com/1154097).
Because CompositingReason::kSVGRoot is for pre-CompositeAfterPaint
CompositeSVG only to create a GraphicsLayer with
ShouldCreateLayersAfterPaint, this CL also disable the logic for
CompositeAfterPaint.
Bug: 1152691
Change-Id: Ic194501698c0afd5a058647344f812077ed07709
--
wpt-commits: 545c70be7ba0f19e557b529ebb8fdf6e56eeb3cd
wpt-pr: 26705
Automatic update from web-platform-tests
[css-multicol] move tests from vendor-imports into the main suite (#26722)
These tests pass everywhere, and have no tricky dependencies.
Part of https://github.com/web-platform-tests/wpt/issues/8615.
--
wpt-commits: 2b631b86937343a916fcd49eb11a518b2b064f85
wpt-pr: 26722
Automatic update from web-platform-tests
[css-flex] Port some mozilla tests to check-layout
These files, from
external/wpt/css/vendor-imports/mozilla/mozilla-central-reftests/flexbox/flexbox-align-content*
have ~70 test cases each. Chrome fails some of them but not others. With
check-layout we can use -expected.txt files to prevent regressions for
the cases that we pass. With the current ref tests, we have to disable
an entire file if we fail even one case in it.
Change-Id: If82f455a22745898b0acf59c0f7cd20b525951cb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568816
Reviewed-by: Christian Biesinger <cbiesinger@chromium.org>
Commit-Queue: David Grogan <dgrogan@chromium.org>
Cr-Commit-Position: refs/heads/master@{#832876}
--
wpt-commits: 3b3569632df0fcfc2313d8618c99fd65cae848fa
wpt-pr: 26712
Automatic update from web-platform-tests
URLPattern: Add initial binding implementation.
This CL adds the initial binding for URLPattern and partially implements
the test() method. It includes some WPT tests, but will need additional
tests.
Bug: 1141510
Change-Id: Id6a0482915f74a37504cf45102d89d14373f2489
Binary-Size: Size increase is due to this CL happening to be first to use a number of abseil library bits.
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2545862
Commit-Queue: Ben Kelly <wanderview@chromium.org>
Reviewed-by: Jeremy Roman <jbroman@chromium.org>
Cr-Commit-Position: refs/heads/master@{#832852}
--
wpt-commits: a4ae4db28abbfb97f9f8df5eb0af75125cd3fdd2
wpt-pr: 26651
Automatic update from web-platform-tests
[top-level await] Prohibit top-level await in service workers
This CL disallows top-level await for service workers by
terminating the worker.
The error that's thrown when Run Service Worker fails is changed
to a TypeError per the spec draft for top-level await integration [0].
Note that this also changes the sudden termination errors that were
previously AbortErrors to TypeErrors.
[0] https://github.com/w3c/ServiceWorker/pull/1444
Bug: 1129795
Bug: 1022182
Bug: v8:9344
Change-Id: Ia764ab553b88e52d48125f23632dc77f4c256009
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2454306
Commit-Queue: Shu-yu Guo <syg@chromium.org>
Reviewed-by: Dominic Farolino <dom@chromium.org>
Reviewed-by: Makoto Shimazu <shimazu@chromium.org>
Reviewed-by: Hiroshige Hayashizaki <hiroshige@chromium.org>
Cr-Commit-Position: refs/heads/master@{#832849}
--
wpt-commits: aa77795ebe17dc0d7c3259a3fe92023b9da62d3e
wpt-pr: 26019
Automatic update from web-platform-tests
Adjust the part_start when the ShapeResultView is RTL
When creating a new ShapeResultView under RTL mode, the segments
process in the ShapeResultView::AddSegments are passed in reverse order.
This implies that the in case of multiple parts, the first RunInfoPart
may have an offset_ bigger than the start_index_.
When creating a new ShapeResultView instance from the one described
above as source, like we do in the NGLineBreaker::TruncateLineEndResult,
we will use the source's run that were placed in reverse order. We are
determining the part_start of this first RunInfoPart for the new result
based on the the start_index_ of the source's first run. We'll then
calculate the run_start based on this part_start value, subtracting
the above mentioned run's offset_.
However, as we stated before, in case of a source result under RTL
and multiple results, this offset_ value will be greater than the
start_index_, leading to a possible arithmetic overflow when
computing the run_start value.
Bug: 1152387
Change-Id: Ic69740497543b1d2d4dd8bf20d3f1b6c5de46bcc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567215
Commit-Queue: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#832795}
--
wpt-commits: 13bade5077c754d3d42183606772a060f54cbe29
wpt-pr: 26709
Automatic update from web-platform-tests
Keep ReadableStreamDefaultReader alive if it has pending requests.
If the only reference to a ReadableStreamDefaultReader is from
javascript code that is used as fulfillment handler for its "read"
promise the reader can get garbage collected, resulting in the promise
never resolving. This fixes that issue by making
ReadableStreamDefaultReader implement HasPendingActivity to return true
if there are any pending read promises.
Bug: 1092048
Change-Id: Iccf2d6db453c6a27c82542af7a1dc1a2d792c3ef
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2561043
Reviewed-by: Adam Rice <ricea@chromium.org>
Reviewed-by: Yutaka Hirano <yhirano@chromium.org>
Commit-Queue: Marijn Kruisselbrink <mek@chromium.org>
Cr-Commit-Position: refs/heads/master@{#832599}
--
wpt-commits: 2f95271debcba3e26e7294beeee4fa5a2ecfbfa0
wpt-pr: 26649
Automatic update from web-platform-tests
Fix the failure of css-scroll-snap/snap-at-user-scroll-end-manual.html
The scroll-snap-type property should be set on <html> rather than
<body>, because scroll-snap-type should not be propagated from body
element to the viewport, we should use its value on html instead.
Bug: 984438
Change-Id: I9b42289cc217ae3d9b4aafc69171a16087a24de0
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2568433
Reviewed-by: David Bokan <bokan@chromium.org>
Commit-Queue: Lan Wei <lanwei@chromium.org>
Cr-Commit-Position: refs/heads/master@{#832567}
--
wpt-commits: 44616b968cd348611b013e3d92ad135133623fce
wpt-pr: 26706
Automatic update from web-platform-tests
Add interfaces/performance-measure-memory.idl and test (#26415)
Test is marked tentative to match the rest of the tests in the
directory.
Closes https://github.com/web-platform-tests/wpt/pull/26361
--
wpt-commits: 2a864580217bbe93bf04a302be73c627436df8f3
wpt-pr: 26415
Automatic update from web-platform-tests
Fix too small scale during animation without scale but with ancestor scale
Previously during a translation animation, as the animation didn't have
scale, we would fallback to use the native scale. In cases that the
animating element had a big accumulated scale from ancestors, the scale
would be too small compared to the ideal scale.
Another failure case was that when a big animation scale would cause the
rasterized layer to be larger than the viewport, we would also fallback
to use the native scale, which might be also too small if the layer had
a big accumulated scale from ancestors.
Now don't adjust scale for transform animation if the animation doesn't
animate scale. And don't fallback to native scale when the scale is too
big, but calculate a scale that just makes the rasterized layer not
larger than the viewport.
Bug: 1153428
Change-Id: I4a4f3133b01099752629f6710c8375a7b715ab0b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566053
Reviewed-by: vmpstr <vmpstr@chromium.org>
Commit-Queue: Xianzhu Wang <wangxianzhu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#832491}
--
wpt-commits: 8a5a3c901357b86c49ac39a7f856311c0b71df39
wpt-pr: 26686
Automatic update from web-platform-tests
[wptrunner/Chromium] Split out test messages into stderr
This only affects the Chromium log formatter of wptrunner.
We want to produce a valid metadata and full logs separately, the former
as the "-expected.txt" artifact and the latter as "-stderr.txt".
Bug: 1154085
Cq-Include-Trybots: luci.chromium.try:linux-wpt-identity-fyi-rel,linux-wpt-input-fyi-rel
Change-Id: I059e05005d2b5f72708c783c5c81deaa86f8b417
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2567094
Commit-Queue: Robert Ma <robertma@chromium.org>
Reviewed-by: Luke Z <lpz@chromium.org>
Cr-Commit-Position: refs/heads/master@{#832486}
--
wpt-commits: 17af9e57e8b6fadafede239a1ac04bd86890167e
wpt-pr: 26687
Automatic update from web-platform-tests
Fix SVG filter data invalidation for empty containers
Empty containers will fail to create FilterData because they have an
empty bounding box. When children were added to the container, making
the bounding box non-empty we would fail to mark the paint properties as
needing update because of the check for existing FilterData in
SVGElementResourceClient::InvalidateFilterData().
Instead always dispose of the filter data and mark paint properties for
update, and use the |filter_data_dirty_| flag as an early-out check.
Since we can now call InvalidateFilterData() directly in
SVGElementResourceClient::ResourceElementChanged(), fold
ClearFilterData() into InvalidateFilterData().
Bug: 1154050
Change-Id: I01c8ebac4f62532e2c17aabc3d998d7601dbb71b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2566992
Reviewed-by: Xianzhu Wang <wangxianzhu@chromium.org>
Commit-Queue: Fredrik Söderquist <fs@opera.com>
Cr-Commit-Position: refs/heads/master@{#832391}
--
wpt-commits: d2137c1a81095c78c1c227b379b6690af33c1240
wpt-pr: 26695
Gregory Mierzwinski
Mihai Alexandru Michis
Kevin Jacobs
James Graham
moz-wptsync-bot
Kent Tamura
Reilly Grant
Lan Wei
autofoolip
Harald Alvestrand
Hiroshige Hayashizaki
Arthur Hemery
Benjamin Gruenbaum
Olivier Yiptong
David Van Cleve
Xianzhu Wang
Nicolás Peña Moreno
Philip Jägenstedt
David Grogan
Ben Kelly
Domenic Denicola
Shu-yu Guo
Javier Fernández García-Boente
Marijn Kruisselbrink
Stephen McGruer
Robert Ma
Fredrik Söderqvist