Closed Bug 872301 Opened 11 years ago Closed 8 years ago

enable ability to switch between longhand/shorthand behavior based on pref

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: jtd, Unassigned)

References

(Blocks 1 open bug)

Details

The style/DOM system now has the ability to expose new CSS properties based on a pref. For longhand properties this works just fine but it's tricky/non-trivial to do for a shorthand property. I ran into this working on the new subproperties of font-variant that enable font features from the CSS3 Fonts spec. Existing property: font-variant (longhand) New properties: font-variant (shorthand!) font-variant-caps, font-variant-ligatures, etc. (longhand) Maybe I'm missing an obvious way of doing this but I think at a minimum we need to adjust the macros to allow for a longhand/shorthand switch based on a pref, figure out what OM changes are needed and verify the testing infrastructure supports this (e.g. does property_database.js need additional structure or does the existing SpecialPowers.getBoolPref("layout.css.xxx.enabled") pattern suffice?). This isn't the only example of this, switching a longhand property to a shorthand with more subproperty controls exists in other CSS3 specs.
We ended up not needing this to ship font-variant-*. (For mask, we used a compile-time flag instead of run-time.) Given the amount of work here, I'm inclined to wontfix this.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.