`udtitvfmt_formatToResult` and `udtitvfmt_formatCalendarToResult` were both
promoted to stable in ICU 69, so we can remove the `U_HIDE_DRAFT_API` for this
code.
Depends on D116972
Differential Revision: https://phabricator.services.mozilla.com/D116973
Re-run
```
./make_intl_data.py numbering
./make_intl_data.py units
./make_intl_data.py langtags
./make_intl_data.py tzdata
```
to update numbering systems, measurement units, language tags, and time zone data.
Also remove the "US/Pacific-New" link from `otherICULegacyLinks()` because it
is no longer needed. Output from `./make_intl_data.py tzdata` with the link
still present:
```
Info: Link 'US/Pacific-New -> America/Los_Angeles' can be removed from otherICULegacyLinks()
```
Depends on D116968
Differential Revision: https://phabricator.services.mozilla.com/D116969
Also includes an upgrade to glean_parser.
Enables GIFFT as well, mapping between Glean's custom distribution and
Firefox Telemetry's linear or exponential histograms directly.
Differential Revision: https://phabricator.services.mozilla.com/D117420
We want to make our best effort to delete all files we can before we unlock the profile. This includes a retry loop hoping that whoever else locked those files did so intermittently.
And once the profile is unlocked, we want to reduce as much as possible the possibility to interfere with a starting instance on the same profile directory.
Until bug 1716291 lands, we need to get back here to finish the work, but this patch is already supposed to mitigate some of the problems we might see in the wild.
Differential Revision: https://phabricator.services.mozilla.com/D116834
- Don't remove popup from widget hierarchy on nsWindow::Destroy() but leave nsWindow::Show(false) do the job.
- Don't check popup widget visibility from Gtk as it's not reliable.
Differential Revision: https://phabricator.services.mozilla.com/D117601
- Replace DMABufSurfaceWrapper array by FFmpegVideoFramePool and create it only when DMABuf/VA-API is used.
- Use FFmpegVideoFramePool to allocate/recycle video frames backed by DMABuf surfaces.
- Enable SW decoding to DMABuf surfaces only when VA-API is enabled to avoid potential breakage (keep recent state).
- Disable VA-API / DMABuf decoding when WebRender is not used.
- Remove DMABufSurfaceWrapper class.
Differential Revision: https://phabricator.services.mozilla.com/D117223
- Implement abstract class for video frames named VideoFrameSurface
- Implement VideoFrameSurfaceDMABuf class for video frames uploaded to DMABuf memory from SW decoding.
- Implement VideoFrameSurfaceVAAPI class for video frames decoded by VA-API.
- Implement VideoFramePool to create and recycle video frames.
Depends on D117221
Differential Revision: https://phabricator.services.mozilla.com/D117222
- Split VA-API / DMABuf video images decoding to CreateImageDMABuf() and CreateImageVAAPI(). CreateImageVAAPI() is used for VA-API only and CreateImageDMABuf() for images decoded by SW and uploaded to DMABuf.
- Implement FFmpegVideoDecoder::InitHWDecodingPrefs() where VA-API related prefereces are processed.
- Change mDisableHardwareDecoding to mEnableHardwareDecoding for better readability.
- Implement nsDMABufDevice::IsDMABufVideoEnabled() to explicitly configure dmabuf texture setup.
- Remove unused AllocateYUV420PVideoBuffer() prototype.
Differential Revision: https://phabricator.services.mozilla.com/D117220
The docs task takes 20 minutes in our CI, and we don't need it.
This also makes --patch work like --target (cleaner in the yaml)
Differential Revision: https://phabricator.services.mozilla.com/D105811
Automatic update from web-platform-tests
Make DCHECK() about signs of w test the same condition the caller does.
This changes the DCHECK() that tests that the signs of h1.w() and h2.w()
are different to test exactly the same condition that the callers test.
While it looks equivalent, it's different in the cases where the values
are not finite, which fuzzers have (unfortunately) managed to hit, and
which we should probably eventually address in a better way (given that
it's undefined behavior in C++).
Fixed: 1217813
Change-Id: I5b268dad8a2c2435789b00620ca0bd3cdd7bb919
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2956400
Commit-Queue: David Baron <dbaron@chromium.org>
Reviewed-by: Robert Flack <flackr@chromium.org>
Cr-Commit-Position: refs/heads/master@{#892200}
--
wpt-commits: ca6913e021a3ade77e4b5f0aa5d650abef568843
wpt-pr: 29349
Automatic update from web-platform-tests
WebXR: fix regression in obtaining pose between targetRay and grip space
Introduces a change to native origins to be able to distinguish between
input-source-derived grip space origin and target ray space origin.
Since the native origins of those 2 spaces were identical, the change
introduced in https://crrev.com/c/2803481 caused them to be treated as
the same space, thus resulting in returning identity pose from
XRFrame::getPose() method.
Also adds a WPT test that would've caught this regression.
Other minor changes:
- converted if-elseif-else chain into a switch statement
Fixed: 1214497
Change-Id: I66e18b863b2769fce6c8126b5d0ddade99fe9b25
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2953960
Commit-Queue: Piotr Bialecki <bialpio@chromium.org>
Reviewed-by: Alexander Cooper <alcooper@chromium.org>
Reviewed-by: Daniel Cheng <dcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#892183}
--
wpt-commits: bc614ca73eb8b7e73faa61f7878a888530b63ed8
wpt-pr: 29336
Automatic update from web-platform-tests
[TransformInterop] Make blocks whose DOM parent is an inline follow DOM tree.
When the TransformInterop feature is enabled, 3D scene extension
(transform-style: preserve-3d) and the perspective property should
follow the DOM tree. This makes that happen for blocks (or, really, any
non-inlines) whose DOM parent is an inline.
Bug: 1008483
Change-Id: I5bcd6d7087c28639a053b686f90880d94f4c6986
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2956891
Reviewed-by: Koji Ishii <kojii@chromium.org>
Reviewed-by: Chris Harrelson <chrishtr@chromium.org>
Commit-Queue: David Baron <dbaron@chromium.org>
Cr-Commit-Position: refs/heads/master@{#892164}
--
wpt-commits: f0b94497ad7b6ee103310f9e493386764e975863
wpt-pr: 29352
Automatic update from web-platform-tests
New test for summary element as list item (#29341)
--
wpt-commits: a8e5772a0f1c4d666acc5aee2423c38da7c9a71c
wpt-pr: 29341
Automatic update from web-platform-tests
Update URL for MathML Core (#29358)
Spec now developed by Math Working Group. Repository moved to W3C organization
accordingly.
--
wpt-commits: 83e82630d4af4e1c31c03c1cfc3b424d7f805ab4
wpt-pr: 29358
Automatic update from web-platform-tests
[BreakoutBox] Stop MSTGenerator in test
MediaStreamTrackProcessor-video.https.html was faling on the WebKit Linux Leak bot due to a generator not being closed.
Change-Id: I72d56611ec419fa0d700bd1bf0803ed007d3a46d
Fixed: 1219040
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2960248
Commit-Queue: Roberto Carrillo <robertocn@chromium.org>
Reviewed-by: Roberto Carrillo <robertocn@chromium.org>
Cr-Commit-Position: refs/heads/master@{#891990}
--
wpt-commits: e1a723314f3c43edd94758ddba0e5dd715e352f7
wpt-pr: 29357
Automatic update from web-platform-tests
Run mypy for tools/serve/ (but still allow untyped defs)
Part of https://github.com/web-platform-tests/wpt/issues/28833.
--
wpt-commits: 9cbcc977a22a6fe04af23be0876823fb5d5c3d8f
wpt-pr: 28988
Automatic update from web-platform-tests
bind-gen: Enable the new IDL dictionary implementations
Enables the new IDL dictionary implementations.
The APIs are compatible and no major difference, but there are
minor differences between the old and new IDL dictionary
implementations:
1. Exact distinction between "missing" and IDL null.
(dict->foo() is invalid when !dict->hasFoo().)
2. Use the new IDL unions and the new IDL enumerations as
member types of the IDL dictionaries.
3. Move support for (Heap)Vector members.
The pinpoint result:
https://pinpoint-dot-chromeperf.appspot.com/job/1484ae38320000
bind-gen: switch
Bug: 839389
Change-Id: I5fddb608d9a43685963410861955bbd63162935b
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2928684
Commit-Queue: Yuki Shiino <yukishiino@chromium.org>
Reviewed-by: Mike West <mkwst@chromium.org>
Reviewed-by: Kentaro Hara <haraken@chromium.org>
Reviewed-by: Kinuko Yasuda <kinuko@chromium.org>
Cr-Commit-Position: refs/heads/master@{#891914}
--
wpt-commits: 9d65d22e4111c164a4eb753e2994ad74781ffdae
wpt-pr: 29325
Automatic update from web-platform-tests
[BreakoutBox] Replace MSTP::is_pending_pull_ with a counter
|is_pending_pull_| was used to make sure that frames were made available
to the stream only if there was a pending pull request.
However, if multiple pull requests are issued and then no more pull
requests arrive, some of the corresponding read requests will remain
unsettled when |is_pending_pull_| becomes false.
This CL fixes this by replacing the boolean |is_pending_pull_| with a
counter.
Bug: 1218120
Change-Id: I0ffc038a73a6cd1d387dc17e9c21f2c62fc50613
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2950171
Commit-Queue: Guido Urdaneta <guidou@chromium.org>
Reviewed-by: Thomas Guilbert <tguilbert@chromium.org>
Cr-Commit-Position: refs/heads/master@{#891735}
--
wpt-commits: 54a8d29bb4fee70eb1e34956069ebdfa23906d24
wpt-pr: 29339
Automatic update from web-platform-tests
Change |RebuildFragmentTreeSpine| to check |PhysicalFragmentCount|
This patch changes |RebuildFragmentTreeSpine| to check
|PhysicalFragmentCount| instead of |CanUseNewLayout|.
This is consistent with the change for the subtree layout in
r890653 crrev.com/c/2934743, and can handle flow threads
correctly, because flow threads are not |LayoutNGMixin| even
when NG block fragmentation is enabled.
Bug: 965639, 829028
Change-Id: I8c9cdb16e37e67b7a0a9b0665e633d8eb200395d
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2952733
Reviewed-by: Javier Fernandez <jfernandez@igalia.com>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Commit-Queue: Koji Ishii <kojii@chromium.org>
Cr-Commit-Position: refs/heads/master@{#891728}
--
wpt-commits: e4979f6211d11c2614a70cc5231773f9c6e9be85
wpt-pr: 29337
Automatic update from web-platform-tests
Viewport propagation of forced-color-adjust
Forced-color-adjust propagates from the root to the viewport but not
from the body, per the resolution in the following spec issue:
https://github.com/w3c/csswg-drafts/issues/6307
This CL also moves the call for Document::UpdateForcedColors() earlier
in Document::Initialize() to ensure the state of forced colors mode
is set early enough when determining the background-color of the
viewport in forced colors mode.
Bug: 1212201
Change-Id: Ib8109659083d21e1c29fc8bdae519393cb417688
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2915382
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Commit-Queue: Alison Maher <almaher@microsoft.com>
Cr-Commit-Position: refs/heads/master@{#891653}
--
wpt-commits: 2577ffbd3fb4a79766cfa03b1ae976fe446f4aa3
wpt-pr: 29321
André Bargull
Sebastian Hengst
Jan-Erik Rediger
Dragana Damjanovic
Julian Descottes
Iulian Moraru
Jens Stutte
stransky
Alexandru Michis
Jeff Muizelaar
Marian-Vasile Laza
Alexis Beingessner
moz-wptsync-bot
L. David Baron
Piotr Bialecki
youennf
Sergio
Philip Jägenstedt
Rune Lillesveen
François Daoust
Guido Urdaneta
wpt-pr-bot
Yuki Shiino
Koji Ishii
Sahir Vellani
Alison Maher