Open
Bug 1366536
Opened 7 years ago
Updated 2 years ago
stylo: Decide whether we should check important rule changes for all properties or not
Categories
(Core :: CSS Parsing and Computation, enhancement, P4)
Core
CSS Parsing and Computation
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox57 | --- | wontfix |
People
(Reporter: hiro, Unassigned)
Details
In bug 1334036, we are checking important rule changes for *all* properties and creating SequentialTask if there are any important rule changes, and request a restyle in the SequentialTask. But we don't effectively use the information (I mean the important rule changes for *all* property). If we have such information, we should fix bug 1300982 or bug 1300983. That's being said, the check (and creating SequentialTask and request restyle) pays some amount of costs, I don't think it's a good idea that the costs are included in stylo release, we should do it apart from stylo release. So, I'd suggest to check important rule changes only for opacity and transform properties before creating the SequentialTask. Brian, what do you think?
Reporter | ||
Updated•7 years ago
|
Flags: needinfo?(bbirtles)
Comment 1•7 years ago
|
||
If we only need to do it for opacity and transform for now to preserve current behavior I agree we should do that.
Flags: needinfo?(bbirtles)
Updated•7 years ago
|
Priority: -- → P2
Updated•7 years ago
|
Priority: P2 → --
Comment 2•7 years ago
|
||
Nice to have, P4. If this is an important optimization, please let me know.
Priority: -- → P4
Comment 3•7 years ago
|
||
status-firefox57=wontfix unless someone thinks this bug should block 57
status-firefox57:
--- → wontfix
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•