Note: There are a few cases of duplicates in user autocompletion which are being worked on.

stylo: Decide whether we should check important rule changes for all properties or not

NEW
Unassigned

Status

()

Core
CSS Parsing and Computation
P2
normal
2 months ago
a month ago

People

(Reporter: hiro, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

2 months ago
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

2 months ago
Flags: needinfo?(bbirtles)
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)
Priority: -- → P2
You need to log in before you can comment on or make changes to this bug.