Per https://bugzilla.mozilla.org/show_bug.cgi?id=1080889#c3 is Navigator.getMobileIdAssertion one of the only APIs that marks LOOP and 2.0+ only. WebRTC and other APIs are pre 2.0. Supporting feature detecting this one API will limit the app to 2.0+ devices as expected and can be done using Navigator.hasFeature and api.window.Navigator.getMobileIdAssertion .

where is getMobileIDAssertion documented as a webapi? I believe that if hasFeature needs to be enhanced, then it would need to get into platform - and it would be in Firefox OS 2.2 - so I think we will need a workaround, like detecting something else that is in 2.0 or above, not using hasfeature. For instance, detecting whether the hasFeature API exists.

Navigator.getMobileIdAssertion can be detected using hasFeature('api.window.Navigator.getMobileIdAssertion'). When did api.window.Navigator.getMobileIdAssertion land?

The work on that API was done in bug 1021594.

Sounds like we're in good shape then. Thanks for investigating, Harald.

Why is this marked as major? Does this actually block LOOP?

(In reply to Christopher Van Wiemeersch [:cvan] from comment #5) > Why is this marked as major? Does this actually block LOOP? Ah, bug 1080889. I answered my own question.

Removing the dependency to Bug 988276 - (loop_mobile) [meta] Loop mobile client version 1.1 for release 2.0 in FxOS, as bug 1080889 already blocks it

Was done in bug 1097429, bug 1097424 and others.