Bug 900241 added the ability to detect some manifest fields and their support in a given b2g version, but for 2.5 we also need a way to detect the new role:"homescreen"

[Blocking Requested - why for this release]: Required by the marketplace to avoid presenting homescreen apps to users on <2.5 devices, where replaceable homescreens are not supported.

Can the version number be used as a key instead?

(In reply to Andrew Overholt [:overholt] from comment #2) > Can the version number be used as a key instead? I think the Marketplace team is looking to avoid inferring specific feature support from a version number. But I'll let :ddurst respond as he is on the receiving end of this

Comment on attachment 8677590 [details] [diff] [review] Expose replaceable homescreen feature Review of attachment 8677590 [details] [diff] [review]: ----------------------------------------------------------------- This one also needs a test.

(In reply to Sam Foster [:sfoster] from comment #3) > (In reply to Andrew Overholt [:overholt] from comment #2) > > Can the version number be used as a key instead? > > I think the Marketplace team is looking to avoid inferring specific feature > support from a version number. But I'll let :ddurst respond as he is on the > receiving end of this Indeed we are looking to avoid inferring specific feature support from a version number, but also looking to the manifest role because that is the (only) indicator that differentiates a homescreen "app" from a regular webapp -- iow, it's a required manifest value for the homescreen content type.

mars, ddurst and I ended up chatting. In order to test this, launch the dev version of the marketplace, and search :debug The flag for detections are down below.

All the hasFeature() checks are there: addonsEnabled, homescreensEnabled, and lateCustomizationEnabled. If the checks return True, they'll be true.