Unfortunately this is not currently maintained (it's been broken
since the addition of sub_slice compositor surface support).
It's also complicating efforts underway to refactor the way that
picture cache dependencies are handled as part of the visibility
pass refactoring work.
For these reasons, let's remove this functionality. If we find
someone with time to maintain it in future, it's likely that we
could restore most of the viewer code, and update the picture
cache code in WR to output the appropriate information.
Differential Revision: https://phabricator.services.mozilla.com/D131105
Currently we're falling back when hitting an uninitialized filter (e.g. a bad
url) and the fallback path just draws nothing. We can do that just as well by
drawing nothing ourselves.
Differential Revision: https://phabricator.services.mozilla.com/D130281
This patch potentially changes the behavior when the scrolled frame is in
vertical writing-mode, but it should be the correct way to handle the scrollbar
change.
Differential Revision: https://phabricator.services.mozilla.com/D130711
This updates the non-localized strings that appear in the Firefox Suggest
preferences UI with the final approved strings.
Differential Revision: https://phabricator.services.mozilla.com/D131031
LineBreaker::Strictness is just an alias of LineBreakRule in Segmenter.h. This
is to reduce the dependency of the legacy LineBreaker.
Differential Revision: https://phabricator.services.mozilla.com/D131026
LineBreaker::WordBreak is just an alias of WordBreakRule in Segmenter.h. This is
to reduce the dependency of the legacy LineBreaker.
Differential Revision: https://phabricator.services.mozilla.com/D131025
In recent version of espeak-ng/speechd the language field is accurate
and doesn't need to be amended with the variant field.
The variant field seems to be the speaker's name which we don't have an
equivalent field for in the DOM voice object.
On my system speech-dispatcher lists 109 languages and 79 "variants".
It then applies each variant (eg. Denis, Boris, Steph) to each language
resulting in 8,611 voices.
Differential Revision: https://phabricator.services.mozilla.com/D130937
The problem here is a race: Even though the user is enrolled in the online
scenario via Nimbus, the Nimbus urlbar variables may not be initialized by the
time we migrate Suggest preferences on startup. The data-collection pref is set
when we [migrate prefs](https://searchfox.org/mozilla-central/rev/df6434d2ebfdf2b5f89f205fc81d60d64a774fe1/browser/components/urlbar/UrlbarPrefs.jsm#872) -- and only there --
so we're not hitting that path like we should be. That's because the scenario
can still be the default value of "offline".
Fortunately the Nimbus client API gives us a ready promise we can await that is
resolved when the feature is loaded and ready, so all we need to do is await it
before trying to update the scenario and do migrations.
Differential Revision: https://phabricator.services.mozilla.com/D131065
When application/x-moz-file-promise MIME content is adverised, save the file to /tmp/dnd_file-*/ directory and
offer it as text/uri-list MIME type.
Based on patch by Tobias Koenig.
Differential Revision: https://phabricator.services.mozilla.com/D130767
Automatic update from web-platform-tests
[FlexNG] Set MinSizeShouldEncompassIntrinsicSize
SetMinBlockSizeShouldEncompassIntrinsicSize() on a flex item
to allow the item to grow as a result of fragmentation.
In order for this flag to have an effect on flex items inside
a column flex container, we also had to SetIsFixedBlockSize()
to false.
This will be used to expand the flex lines if needed.
Bug: 660611
Change-Id: I8890cc54262c14664706b9cb9efb141a453dceff
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3276791
Commit-Queue: Alison Maher <almaher@microsoft.com>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Morten Stenshorne <mstensho@chromium.org>
Cr-Commit-Position: refs/heads/main@{#941410}
--
wpt-commits: dc91bc44ac13e268173db8afe9ee7eb6cfbf73d1
wpt-pr: 31611
Automatic update from web-platform-tests
Add test for layout containment inside a fit-content parent (#31617)
--
wpt-commits: 274541188260b060f4f060b72a30f1dabd3c78b8
wpt-pr: 31617
Automatic update from web-platform-tests
[inert] Let modal dialogs make the root element inert
From https://html.spec.whatwg.org/multipage/interaction.html#inert,
> A Document document is blocked by a modal dialog subject if subject is
> the topmost dialog element in document's top layer. While document is
> so blocked, every node that is connected to document, with the
> exception of the subject element and its shadow-including descendants,
> must be marked inert.
This doesn't exclude the root element, so it should also be inert.
Simply doing this change would break these tests:
- html/dialog/modal-dialog-ancestor-is-inert.html
- html/dialog/modal-dialog-blocks-mouse-events.html
Excluding the root element in HitTestResult::SetInnerNode avoids that.
Note I plan to track inertness in ComputedStyle, and then remove both
Node::IsInert and hit test retargeting for inert. So this patch is just
temporary, to align with the final behavior.
Also note that only the the root element (documentElement) is affected.
The root node (document), represented as rootWebArea in a11y, will still
not become inert when there is a modal dialog or fullscreen element.
Bug: 692360
TEST=All/DumpAccessibilityTreeTest.AccessibilityModalDialogOpened/blink
TEST=All/DumpAccessibilityTreeTest.AccessibilityModalDialogStack/blink
TEST=All/DumpAccessibilityTreeTest.AccessibilityOpenModal/blink
TEST=external/wpt/html/semantics/interactive-elements/the-dialog-element/inert-node-is-unfocusable.html
Change-Id: I8ce7905a85e386fae6163423f5e078b6c4588db1
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3263132
Commit-Queue: Oriol Brufau <obrufau@igalia.com>
Reviewed-by: Aaron Leventhal <aleventhal@chromium.org>
Reviewed-by: Nektarios Paisios <nektar@chromium.org>
Reviewed-by: Rune Lillesveen <futhark@chromium.org>
Reviewed-by: Mason Freed <masonf@chromium.org>
Cr-Commit-Position: refs/heads/main@{#941302}
--
wpt-commits: 0457111e7109ec3d9e575aa421b96d8c36ce2ae8
wpt-pr: 31533
Automatic update from web-platform-tests
Move move-after-transition.html to WPT
Removed unused styles. Converted from a pixel test to asserts. Ensure
initial transition is triggered, and that there is no additional
transition after setting transition-property to 'none'.
Bug: 1267553
Change-Id: I302709dee4990f2871d6c248852bd23993cda754
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3275545
Reviewed-by: Steve Kobes <skobes@chromium.org>
Commit-Queue: Kevin Ellis <kevers@chromium.org>
Cr-Commit-Position: refs/heads/main@{#941300}
--
wpt-commits: 26bb6529ea8b19b93a1f878ebba79353f87d4da0
wpt-pr: 31616
