Confirmed users
746
edits
Marketplace/getFeature: Difference between revisions
Jump to navigation
Jump to search
m
slight edits
(added technical synopsis) |
m (slight edits) |
||
| Line 8: | Line 8: | ||
Another point of confusion is the wiki page on <code>hasFeature</code> speaks of [https://wiki.mozilla.org/WebAPI/Navigator.hasFeature#.22manifest.22_namespace values for the manifest namespace that can be used with <code>hasFeature</code>]; but these were actually implemented on <code>getFeature</code> -- which makes sense if you know that <code>hasFeature</code> is not implemented, but is incorrect according to the spec. | Another point of confusion is the wiki page on <code>hasFeature</code> speaks of [https://wiki.mozilla.org/WebAPI/Navigator.hasFeature#.22manifest.22_namespace values for the manifest namespace that can be used with <code>hasFeature</code>]; but these were actually implemented on <code>getFeature</code> -- which makes sense if you know that <code>hasFeature</code> is not implemented, but is incorrect according to the spec. | ||
<code>hasFeature</code> '''does''' exist in 2.1, though it has the [https://bugzilla.mozilla.org/show_bug.cgi?id=1098470 bug where it returns ''undefined'' for manifest.* tests]. There is no plan to backport support of <code>hasFeature</code> to 2.0. | <code>hasFeature</code> '''does''' exist in 2.1, though it has the (recently fixed) [https://bugzilla.mozilla.org/show_bug.cgi?id=1098470 bug where it returns ''undefined'' for manifest.* tests]. There is no plan to backport support of <code>hasFeature</code> to 2.0. | ||
== Technical synopsis of hasFeature/getFeature == | == Technical synopsis of hasFeature/getFeature == | ||
The [https://wiki.mozilla.org/WebAPI/Navigator.hasFeature hasFeature API is documented on the wiki], but it can be summarized: across all versions, | The [https://wiki.mozilla.org/WebAPI/Navigator.hasFeature hasFeature API is documented on the wiki], but it can be summarized: across all versions, | ||
* <code>getFeature</code> works for hardware.memory (expected | * <code>getFeature</code> works for hardware.memory (expected), but nothing else; | ||
* <code>hasFeature</code> works for api.* (expected), doesn't work for hardware.memory (expected | * <code>hasFeature</code> works for api.* (expected), and doesn't work for hardware.memory (expected). | ||
... with the complicating factor being that <code>hasFeature</code> does not exist on 2.0 (even though <code>getFeature</code> does). | ... with the complicating factor being that <code>hasFeature</code> does not exist on 2.0 (even though <code>getFeature</code> does). | ||
| Line 59: | Line 59: | ||
# In order to accommodate the largest group of devices that have Firefox Hello on it (and Where's My Water available to it), we want 2.0 users to update their shipped marketplace with our new one. | # In order to accommodate the largest group of devices that have Firefox Hello on it (and Where's My Water available to it), we want 2.0 users to update their shipped marketplace with our new one. | ||
## Rather than specifically target 2.0, we want to just notify all users if there's an update. | ## Rather than specifically target 2.0, we want to just notify all users if there's an update. | ||
### we can detect that there is an update available for our app already | |||
### we CAN force install the update, no additional permissions necessary | ### we CAN force install the update, no additional permissions necessary | ||
=== The packaged iframe === | === The packaged iframe === | ||