In one place, we specifically check for softfp and do the right thing,
while in another we omit doing it, while at the same time we already
have a check in arm.configure that gives us (mostly) the flags we want.
Differential Revision: https://phabricator.services.mozilla.com/D157687
Make it a bit easier to read and less prone to race conditions. Remove a
setTimeout referencing bug 103197 which I'm pretty sure it's not an
issue.
Differential Revision: https://phabricator.services.mozilla.com/D156543
Make it a bit easier to read and less prone to race conditions. Remove a
setTimeout referencing bug 103197 which I'm pretty sure it's not an
issue.
Differential Revision: https://phabricator.services.mozilla.com/D156543
Create XULButtonElement instead to do the event handling. Pretty much a
straight port, this allows these elements to respect CSS display
properly (and use modern flexbox rather than old XUL layout).
Differential Revision: https://phabricator.services.mozilla.com/D157509
Fixing Perma toolkit/components/aboutperformance/tests/browser/browser_aboutperformance.js | Uncaught exception in test when Gecko merges to Beta on 2022-09-19
Test with pref "toolkit.aboutPerformance.showInternals=false" to have no rows with subitems and trigger the exception.
Differential Revision: https://phabricator.services.mozilla.com/D157484
Some anonymous children are important for properly sizing their parents
even when those parents hide content with `content-visibility`. This is
shown by regressions in the proper layout of some form elements with
`content-visibility`.
This change introduces a more conservative approach for avoiding layout
of hidden content. Instead of leaving all children dirty during reflow,
reflow anonymous frames (and nsComboboxDisplayFrame, a specialized kind
of anonymous frame). This change means that frames may only lay out some
of their children, so it must introduce some more changes to assumptions
during line layout.
In addition, this change renames `content-visibility` related methods in
nsIFrame in order to make it more obvious what they do.
Differential Revision: https://phabricator.services.mozilla.com/D157306
Some anonymous children are important for properly sizing their parents
even when those parents hide content with `content-visibility`. This is
shown by regressions in the proper layout of some form elements with
`content-visibility`.
This change introduces a more conservative approach for avoiding layout
of hidden content. Instead of leaving all children dirty during reflow,
reflow anonymous frames (and nsComboboxDisplayFrame, a specialized kind
of anonymous frame). This change means that frames may only lay out some
of their children, so it must introduce some more changes to assumptions
during line layout.
In addition, this change renames `content-visibility` related methods in
nsIFrame in order to make it more obvious what they do.
Differential Revision: https://phabricator.services.mozilla.com/D157306
xul|menulist:-moz-focusring > xul|*.menulist-label-box can never match, since
the label box is in the shadow tree exposed as a part.
For the same reason the equivalent linux rule isn't needed either (there's
nothing that would set an outline on this).
While at it s/-moz-focusring/focus-visible.
Depends on D157421
Differential Revision: https://phabricator.services.mozilla.com/D157422
The bug here is that the 12px height below wasn't having an effect (flexing
took priority) and now is.
Rather than removing it or what not, just center-align the dropmarker icon,
this works with box layout modes and is more straight-forward.
Differential Revision: https://phabricator.services.mozilla.com/D157421
These macros will produce better outputs when they fail than these existing
patterns using `ENSURE_TRUE(NS_SUCCEEDED(...))` or similar, so this is a bulk
rewrite of existing tests to use them.
It should also help with discoverability when people base their tests off of
other existing tests.
Differential Revision: https://phabricator.services.mozilla.com/D157214
Actually, the midir in mozilla-central isn't able to built for Linux/riscv64.
Although upstreamed midir supports Linux/riscv64 by [*1], our tree version is
old and we cannot update it due to bug 1773189. So we should disable it on
Linux/riscv64.
*1 https://github.com/Boddlnagg/midir/pull/101
Differential Revision: https://phabricator.services.mozilla.com/D157319
Summary row includes an image button to expand/collapse details - it is made focusable with keyboard, programmatic role of a button and a descriptive label are assigned, and keyboard events are provided. Related code was refactored.
Differential Revision: https://phabricator.services.mozilla.com/D137709
This allows them to shrink below their intrinsic size without adding a
bunch of min-height: 0 when using emulated flexbox, by zeroing out their
intrinsic size.
See the attached test-case, which is a very reduced version of
browser.xhtml: contain: size on the iframe seems like a better fix than
making sure all ancestors have min-height: 0 all the way up, which is
kinda what bug 1790303 was aiming for.
Differential Revision: https://phabricator.services.mozilla.com/D157207
Summary row includes a Twisty image button to expand/collapse details - it is made focusable with keyboard, programmatic role of a `button` and a descriptive label are assigned, and keyboard events are provided. Related code is refactored and focus styling is updated.
Tests fixed.
Differential Revision: https://phabricator.services.mozilla.com/D139151
Summary row includes a Twisty image button to expand/collapse details - it is made focusable with keyboard, programmatic role of a `button` and a descriptive label are assigned, and keyboard events are provided. Related code is refactored and focus styling is updated.
Differential Revision: https://phabricator.services.mozilla.com/D139151