Remove host-multiple-006 because it's a bit-identical copy of
host-multiple-002.html.
Add a test for the specific descendant combinator (bug 1950290).
Differential Revision: https://phabricator.services.mozilla.com/D240033
We add NSS_CFLAGS in preparation of equivalent changes to crates that
are vendored in third-party/rust that use netwerk/socket/neqo/extra-bindgen-flags
(that we thus keep around for now).
Differential Revision: https://phabricator.services.mozilla.com/D239831
In the case of "longer hue", even though we're going to consider both sides
of the mix to have the same hue value, we still need to do an interpolation
to find the proper intermediate values; we can't just use a constant hue
across the entire range of the interpolation even though both ends have the
same value.
Differential Revision: https://phabricator.services.mozilla.com/D238772
Pretty bare bones (some properties missing), but this allows the
transition pseudo-elements to be in the right place.
We need to implement live capturing / integrate nical's work to display
the "new" image properly, but we'll get to that. Meanwhile this should
be uncontroversial.
Differential Revision: https://phabricator.services.mozilla.com/D238005
This should be rather uncontroversial. I filed bug 1947747 for inspector
support for this (which should work similarly than for presentational
hints).
Differential Revision: https://phabricator.services.mozilla.com/D237886
Allow querying int and string prefs too via functional syntax:
```
@media -moz-pref("pref-name", <value>) {
```
No argument means the pref exists and has a non-zero/false/empty value.
Unfortunately stylelint is still unhappy with this so we need to keep
the annoying comments...
Differential Revision: https://phabricator.services.mozilla.com/D237275
Reasoning with these functions gets confusing, because anchor
functions can become percentage as well as auto.
Defer optimization for now.
Differential Revision: https://phabricator.services.mozilla.com/D237098
Try to resolve math function nodes with percentage basis of zero. Invalid
anchor functions will make the value Invalid-At-Computed-Value-Time (i.e.
`auto`), so that is handled. Otherwise, `CalcNode` existing indicates use
of percentage values and/or anchor functions. If only anchor functions
are used, we can use the resolved value as-is - otherwise, it must be
re-resolved before its value is queried.
This is of course redundant, and may require some optimization down
the line (We don' eagerly get percentage basis since that requires
ancestor traversal that may be wasted).
Differential Revision: https://phabricator.services.mozilla.com/D237095
Reasoning with these functions gets confusing, because anchor
functions can become percentage as well as auto.
Defer optimization for now.
Differential Revision: https://phabricator.services.mozilla.com/D237098
Try to resolve math function nodes with percentage basis of zero. Invalid
anchor functions will make the value Invalid-At-Computed-Value-Time (i.e.
`auto`), so that is handled. Otherwise, `CalcNode` existing indicates use
of percentage values and/or anchor functions. If only anchor functions
are used, we can use the resolved value as-is - otherwise, it must be
re-resolved before its value is queried.
This is of course redundant, and may require some optimization down
the line (We don' eagerly get percentage basis since that requires
ancestor traversal that may be wasted).
Differential Revision: https://phabricator.services.mozilla.com/D237095
Reasoning with these functions gets confusing, because anchor
functions can become percentage as well as auto.
Defer optimization for now.
Differential Revision: https://phabricator.services.mozilla.com/D237098
Try to resolve math function nodes with percentage basis of zero. Invalid
anchor functions will make the value Invalid-At-Computed-Value-Time (i.e.
`auto`), so that is handled. Otherwise, `CalcNode` existing indicates use
of percentage values and/or anchor functions. If only anchor functions
are used, we can use the resolved value as-is - otherwise, it must be
re-resolved before its value is queried.
This is of course redundant, and may require some optimization down
the line (We don' eagerly get percentage basis since that requires
ancestor traversal that may be wasted).
Differential Revision: https://phabricator.services.mozilla.com/D237095
Allow querying int and string prefs too via functional syntax:
```
@media -moz-pref("pref-name", <value>) {
```
No argument implies bool. Unfortunately stylelint is still unhappy with
this so we need to keep the annoying comments...
Differential Revision: https://phabricator.services.mozilla.com/D237275
Not intended to be a full implementation, but more of an off-by-default
prototype with the right pieces in place.
This parses and evaluates the queries, but:
* They don't evaluate against the right style (I didn't change the
container query lookup yet).
* They're not invalidated properly (this changes selector matching as a
result of style changes which is not currently dealt with).
Still I want to get this in since it's kinda straight-forward and needed
for the eventual full implementation.
There are some tests that start running now that I'd need to update, try
in progress.
Differential Revision: https://phabricator.services.mozilla.com/D236468
Style system support for the new oblique-only value of font-synthesis-style.
(Applying this during rendering will be the next patch.)
Differential Revision: https://phabricator.services.mozilla.com/D236912
* Spinner and spinner-textfield are totally unused.
* up/down buttons are only used for <input type=number>. The only
number inputs we have in our UI use the non-native theme already (the
print preview dialog).
* Windows already always uses non-native spinner up/down unconditionally, and
linux does it on mismatched color scheme.
We can probably live without native theme support for these. It's
completely unused right now.
Differential Revision: https://phabricator.services.mozilla.com/D236904
