Hi,
I've been told that it would be nice if we had stronger language in our
API exposure guidelines [1] around when we deviate from them. This is
mostly applicable when we expose things to Firefox OS applications. The
changes I propose to the "Special cases" section [2] are:
-There will of course be special cases where we deviate from this
+There may be special cases where we deviate from this
goal. New user-facing products like Firefox OS may need to ship
APIs that have not yet been embraced by other browser engines or
thoroughly discussed by standards bodies. This allows Mozilla to
provide functionality that other browser engines aren't working
on or the majority of the Web community isn't interested in at
that time. Examples of such functionality include telephony and
Bluetooth. This functionality is most often only exposed to
Firefox OS applications of elevated privileges and not via the
Firefox OS browser application.
+It is '''highly unlikely''' that we will expose this functionality
+to the web at large.
If you agree with the intent but have wording suggestions, please send
them to me and let's avoid bikeshedding on the list.
If no one expressed disagreement here by Friday 25 April 2014, I'll make
the changes on the wiki.
Thanks,
Andrew
[1]
https://wiki.mozilla.org/WebAPI/ExposureGuidelines
[2]
https://wiki.mozilla.org/WebAPI/ExposureGuidelines#Special_Cases
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
