| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
|
|
|
|
|
|
|
| |
When we physicalize the declarations for @keyframes, we end up having a physical
declaration with an unparsed value with `from_shorthand` being the logical
shorthand.
Account for this case properly when substituting custom properties, to avoid
panicking.
Differential Revision: https://phabricator.services.mozilla.com/D53663
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For developing properties, we will handle them in an other bug.
Besides, I use an iframe for the test because we create a use counter in
the constructor of Document, which use the prefs to decide what kind of
properties we want to record. So, in the test, we have to reload iframe
to make sure we re-create the document, so does the use counter, to make
sure the prefs work properly.
The two prefs affect the css use counters:
1. layout.css.use-counters.enabled: Allocate use counters, and record
non-custom properties.
2. layout.css.use-counters-unimplemented.enabled: Record all unimplmented
properties into the use counters.
If we disable layout.css.use-counters.enblaed, we don't create use counters
object, so layout.css.use-counters-unimplemented.enabled doesn't work,
either.
Differential Revision: https://phabricator.services.mozilla.com/D43860
|
|
|
|
|
|
| |
::first-line/first-letter/placeholder.
Differential Revision: https://phabricator.services.mozilla.com/D41227
|
|
|
|
|
|
| |
::first-line/first-letter/placeholder.
Differential Revision: https://phabricator.services.mozilla.com/D41228
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D40335
|
|
|
|
| |
Renaming the variable helped make sure I looked at every use.
|
| |
|
| |
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D38586
|
|
|
|
|
|
| |
The assertion in properties.mako.rs ensures I got this right.
Differential Revision: https://phabricator.services.mozilla.com/D37720
|
|
|
|
|
|
|
|
|
| |
Now if you add a new inherited, pref-controlled property, you must
declare whether it can have an effect on scrollbar styles. If no,
then the property will be skipped in the assertions that check
whether our cached styles are equal to those we would compute.
Differential Revision: https://phabricator.services.mozilla.com/D37507
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D35247
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D35831
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D29037
|
| |
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D34738
|
|
|
|
|
|
|
| |
From this point on, the webkit-prefixed CSS features that were previously
protected by this pref will now be unconditionally enabled.
Differential Revision: https://phabricator.services.mozilla.com/D33807
|
|
|
|
|
|
|
|
|
|
|
|
| |
This includes style system and layout update. I add 3 extra reftests
because the original tests use ray() function as the offset-path, but we
don't support it. It'd be better to add tests using a different type of
offset-path.
The spec issue about the serialization:
https://github.com/w3c/fxtf-drafts/issues/340
Differential Revision: https://phabricator.services.mozilla.com/D32212
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D29936
|
|
|
|
|
|
| |
Note that the "loose | normal | strict" values are not yet parsed/implemented.
Differential Revision: https://phabricator.services.mozilla.com/D29817
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D30547
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D20115
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D28763
|
|
|
|
|
|
| |
combined with a case transformation.
Differential Revision: https://phabricator.services.mozilla.com/D27402
|
|
|
|
|
|
|
|
| |
implementation and drop the scroll-snap-type-{x,y} longhands.
Now scroll-snap-type is a longhand property.
Differential Revision: https://phabricator.services.mozilla.com/D21622
|
|
|
|
|
|
|
|
|
| |
The scroll snap strictness is defined in the new spec [1], and the structure
is the exactly same as the old scroll snap type structure.
[1] https://drafts.csswg.org/css-scroll-snap-1/#snap-strictness
Differential Revision: https://phabricator.services.mozilla.com/D21621
|
|
|
|
|
|
|
| |
(-moz-list-reversed:true|false) to propagate <ol reversed> to its relevant descendants.
Bug: 288704
Reviewed-by: emilio
|
|
|
|
|
|
| |
overflow-wrap: anywhere.
Differential Revision: https://phabricator.services.mozilla.com/D21398
|
|
|
|
|
|
| |
https://drafts.csswg.org/css-scroll-snap-1/#scroll-snap-align
Differential Revision: https://phabricator.services.mozilla.com/D20205
|
| |
|
|
|
|
|
| |
Bug: 1520684
Reviewed-by: emilio
|
|
|
|
|
|
| |
https://drafts.csswg.org/css-scroll-anchoring/#exclusion-api
Differential Revision: https://phabricator.services.mozilla.com/D13265
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since it allows to animate display, which is not good.
This is a regression from:
https://hg.mozilla.org/mozilla-central/rev/6884ba750aa3
Actually I wonder if the logic shouldn't be the other way around, i.e., a
shorthand is animatable if all the longhands are, not if just one.
In any case this rolls back to the previous behavior, should we do that, it
should be another bug.
Differential Revision: https://phabricator.services.mozilla.com/D14632
|
|
|
|
|
|
| |
It's one of the most annoying / hacky mako bits we have.
Differential Revision: https://phabricator.services.mozilla.com/D14084
|
| |
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D11876
|
|
|
|
|
|
| |
And respect the computed value of `left` / `right` / etc.
Differential Revision: https://phabricator.services.mozilla.com/D11872
|
|
|
|
|
|
|
|
|
| |
This is the first step to unprefix user-select.
This has no behavior change, it's just a nicer way to do the same thing which
allows us to unship individual values more easily using parse(condition).
Differential Revision: https://phabricator.services.mozilla.com/D11580
|
|
|
|
|
|
| |
Per https://github.com/w3c/csswg-drafts/issues/2682
Differential Revision: https://phabricator.services.mozilla.com/D11328
|
| |
|
|
|
|
|
|
|
| |
There are better ways, plus the existing code didn't handle aliases at
all (not that it needed to, but it's better if it does).
Differential Revision: https://phabricator.services.mozilla.com/D10838
|
|
|
|
|
|
|
| |
This needs to update the "fill-rule" and "clip-rule" to use
predefined_type to avoid some compilation errors.
Differential Revision: https://phabricator.services.mozilla.com/D10142
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D2908
|
|
|
|
| |
Differential Revision: https://phabricator.services.mozilla.com/D2932
|
|
|
|
|
|
| |
always returns the right result.
Differential Revision: https://phabricator.services.mozilla.com/D2931
|
| |
|
|
|
|
|
|
| |
Bug: 1473180
Reviewed-by: emilio
MozReview-Commit-ID: GXlf8JNML4N
|
|
|
|
|
|
|
|
|
| |
The setup is that AnimationValue only contains physical properties, and
we physicalize when building keyframes and transitions.
Bug: 1309752
Reviewed-by: birtles
MozReview-Commit-ID: 9dI20N0LFrk
|
|
|
|
|
|
| |
Bug: 1309752
Reviewed-by: heycam
MozReview-Commit-ID: FAL04K5G948
|