On 07/26/2017 04:58 AM, David Teller wrote:
Well, at least there is the matter of feature detection, for people who
want to write code that will work in more than just Firefox.
moz-prefixing makes it clear that the feature can be absent on some
browsers.
Until the day that said other browser gets forced into implementing
those prefixed names due to reasons such as mass adoption of the
prefixed names by developers. Here is a practical example from recent
history:
https://searchfox.org/mozilla-central/rev/8a61c71153a79cda2e1ae7d477564347c607cc5f/dom/webidl/HTMLInputElement.webidl#224
Cheers,
David
On 26/07/17 05:55, Martin Thomson wrote:
On Wed, Jul 26, 2017 at 6:20 AM, Andrew Overholt <overh...@mozilla.com> wrote:
On Tue, Jul 25, 2017 at 3:06 PM, David Teller <dtel...@mozilla.com> wrote:
Should we moz-prefix moz-specific extensions?
We have been trying not to do that for Web-exposed APIs but maybe the
extensions case is different?
I don't think that it is. If there is any risk at all that someone
else might want to use it, then prefixing will only make our life
harder long term. Good names are cheap enough that we don't need to
wall ours off.
See also https://tools.ietf.org/html/rfc6648
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
