Closed Bug 1364303 Opened 8 years ago Closed 8 years ago

stylo: need support for CSS_PSEUDO_CLASS_ENABLED_IN_UA_SHEETS_AND_CHROME on pseudo-classes

Categories

(Core :: CSS Parsing and Computation, enhancement, P2)

Product:
Core
Component:
CSS Parsing and Computation
Version:
53 Branch
Type:
enhancement

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1381851

People

(Reporter: bzbarsky, Unassigned)

References

Details

Gecko pseudo-classes can be enabled in one of three places: 1) Everywhere (no flags) 2) In UA sheets only (CSS_PSEUDO_CLASS_ENABLED_IN_UA_SHEETS) 3) In UA sheets and chrome sheets (CSS_PSEUDO_CLASS_ENABLED_IN_UA_SHEETS_AND_CHROME) What stylo seems to have, in non_ts_pseudo_class_list is a single flag (PSEUDO_CLASS_INTERNAL) whose behavior, I think, corresponds to CSS_PSEUDO_CLASS_ENABLED_IN_UA_SHEETS. There seems to be no equivalent of CSS_PSEUDO_CLASS_ENABLED_IN_UA_SHEETS_AND_CHROME.
Are we going to support chrome document in Stylo's MVP? If not, I guess this isn't a high priority thing.
> Are we going to support chrome document in Stylo's MVP? The question isn't whether we support chrome _document's_ but whether we support chrome _stylesheets_. We're certainly going to support some of those (e.g. chrome://global/skin/resizer.css better be supported). The question is whether any of them use the relevant pseudo-classes. Just did some spot-checking, and looks to me like :-moz-handler-crashed is used in the pluginproblem bits, and those sheets are pulled into random content documents as needed.
Priority: -- → P3
Priority: P3 → --
Priority: -- → P2
TY's doing this as part of bug 1381851.
Depends on: 1381851
The patches in bug 1381851 has implemented PSEUDO_CLASS_ENABLED_IN_UA_SHEETS_AND_CHROME, so mark this bug as a dup.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.