Drop the moz prefix from the MozCSSKeyframeRule and MozCSSKeyframesRule interfaces

RESOLVED FIXED in Firefox 48

Status

()

defect
RESOLVED FIXED
3 years ago
4 months ago

People

(Reporter: Ehsan, Unassigned)

Tracking

({dev-doc-complete, site-compat})

unspecified
mozilla48
Points:
---

Firefox Tracking Flags

(firefox48 fixed)

Details

Attachments

(1 attachment)

No description provided.
I don't think we can suddenly replace the prefixed version with an unprefixed one.
Keywords: site-compat
What makes you say so? A quick search didn't bring up much more than http://www.cnblogs.com/chaojidan/p/4212925.html and a couple of copies, which all show `var ok = window.MozCSSKeyframeRule || window.WebKitCSSKeyframeRule || window.CSSKeyframeRule;`.
From past experience. For example, when I tried to drop -moz-gradients, we found Google(!) sniffed us and sent only -moz-prefixed gradients.
FWIW I did a search on github and also the add-ons MXR before submitting this patch to see if these prefixed names are being widely used and they don't seem to.
Comment on attachment 8730019 [details] [diff] [review]
Drop the moz prefix from the MozCSSKeyframeRule and MozCSSKeyframesRule interfaces

This isn't even on webidl yet, ick.

r=me; I doubt anyone depends on this naming, since these are not constructible.
Attachment #8730019 - Flags: review?(bzbarsky) → review+
https://hg.mozilla.org/mozilla-central/rev/6b3093fbaa8a
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla48
Thanks, Kohei!
Documentation updated:

https://developer.mozilla.org/en-US/docs/Web/API/CSSKeyframeRule
https://developer.mozilla.org/en-US/docs/Web/API/CSSKeyframesRule

Mentioned on Firefox 48 for developers (someone got there before me). But I did linkify them there and fix some other stuff, so yay me!
Sheppy: we don't list the webidl in interfaces (we link to them in the spec link anyway). Can you remove them? Thank you.
I've removed the 'Syntax' sections from the two pages.

Sebastian
Component: DOM → DOM: Core & HTML
You need to log in before you can comment on or make changes to this bug.