Closed Bug 1302104 Opened 8 years ago Closed 8 years ago

Support CSS property "-webkit-appearance" as an alias of "appearance"

Categories

(Core :: CSS Parsing and Computation, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
firefox51 --- affected

People

(Reporter: dholbert, Assigned: MatsPalmgren_bugz)

References

Details

(Keywords: dev-doc-complete, Whiteboard: [webcompat][fixed by bug 1333482])

Bug 837211 added support for "-webkit-appearance" as an alias of "-moz-appearance" (and various other -webkit aliases). But, we later realized that caused visual regressions (bug 1248975 in particular) since our -moz-appearance implementation doesn't work quite like -webkit-appearance (e.g. bug 605985). So we backed out that aliasing in bug 1249134. So currently we have no "-webkit-appearance" support in any shipping builds. Therefore: I'm filing this bug to cover reimplementing a "-webkit-appearance" --> "-moz-appearance" mapping, once we've addressed bug 605985 (and any other incompatibilities we're aware of). (with the goal of improved web compatibility) The patch here will basically consist of backing out bug 1249134. (i.e. backing out the alias-removal)
Blocks: 1170774
Thanks for filing the bug, Daniel! Please don't forget to set the dev-doc-needed flag accordingly! Sebastian
Keywords: dev-doc-needed
Whiteboard: [webcompat]
See also bug 1333482 for implementing 'appearance' matching the css-ui spec. We should probably fix that bug first, before deciding on what to do about the -webkit- alias.
Depends on: 1333482
This was fixed in bug 1333482, although as an alias for 'appearance' not '-moz-appearance'. (the plan is to disable -moz-appearance in a future release: bug 1351745)
Assignee: nobody → mats
Summary: Support CSS property "-webkit-appearance" as an alias of "-moz-appearance" → Support CSS property "-webkit-appearance" as an alias of "appearance"
Whiteboard: [webcompat] → [webcompat][fixed by bug 1333482]
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.