Closed Bug 755694 Opened 13 years ago Closed 12 years ago

Make Marketplace allow access to apps for non-RT browsers

Categories

(Marketplace Graveyard :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: gerv, Unassigned)

Details

(Keywords: productwanted, Whiteboard: [ddn])

"The web is the platform". Browsers which don't support WebRT should still be able to run Marketplace web apps, browser capabilities permitting. Currently, the Marketplace blocks them from doing so, because it does some form of capability sniffing. https://wiki.mozilla.org/Marketplace/Compatibility says: "A key aspect of Mozilla's Apps project is that apps work anywhere HTML5 works. It's important that the Marketplace similarly works everywhere HTML5 works to allow consumers to acquire apps." Andy McKay said: "The marketplace specifically won't let you install an app because we do capability sniffing and some JS. So I think it's pretty simple to switch it around. I don't see any technical reason this can't all happen, I think it's more a focus on Nightly, Android and lack of resources." Gerv
This seems like more of a WebRT bug - but this again begs the question of whether we are supporting non-RT browsers with the JS shim. We're already including https://myapps.mozillalabs.com/jsapi/include.js on Marketplace - are we okay with enabling it (yet)?
(In reply to Chris Van Wiemeersch [:cvan] from comment #1) > This seems like more of a WebRT bug - but this again begs the question of > whether we are supporting non-RT browsers with the JS shim. We're already > including https://myapps.mozillalabs.com/jsapi/include.js on Marketplace - > are we okay with enabling it (yet)? The marketplace side of this bug would be enabling it (which is what this bug is talking about). If there's changes we need to make our end, then let's get bugs filed and link it to this tracking bug.
(In reply to Jason Smith [:jsmith] from comment #2) > (In reply to Chris Van Wiemeersch [:cvan] from comment #1) > > This seems like more of a WebRT bug - but this again begs the question of > > whether we are supporting non-RT browsers with the JS shim. We're already > > including https://myapps.mozillalabs.com/jsapi/include.js on Marketplace - > > are we okay with enabling it (yet)? > > The marketplace side of this bug would be enabling it (which is what this > bug is talking about). If there's changes we need to make our end, then > let's get bugs filed and link it to this tracking bug. Flagging productwanted for Jen, Ragavan, and Justin to comment. What's the correct behavior on a non-RT browser? Would we go to persona.org/apps?
Keywords: productwanted
Component: Consumer Pages → General
QA Contact: consumer-pages → general
(In reply to Jason Smith [:jsmith] from comment #3) > Flagging productwanted for Jen, Ragavan, and Justin to comment. What's the > correct behavior on a non-RT browser? Would we go to persona.org/apps? Got it. Also, I let the authors of the K9o product requirements know that non-webRT support requirement could be clearer. There are a few more options being explored that what's already on this bug. I'll put it all in a write up and distribute to dev-webapps list for feedback.
Assignee: nobody → fligtar
Whiteboard: [ddn]
Target Milestone: --- → 2012-05-17
Target Milestone: 2012-05-17 → 2012-05-31
Product is interested in responding to this bug with official language. I'm removing it from the dev tracking milestones.
Target Milestone: 2012-05-31 → ---
clouserw: who from Product is responsible for taking this bug forward? Gerv
(In reply to Gervase Markham [:gerv] from comment #6) > clouserw: who from Product is responsible for taking this bug forward? > > Gerv Ragavan or fligtar
ragavan/fligtar: what's your plan here? Does "respond with official language" mean "add a notice to the site explaining to users of other web browsers why they can't use the web apps", or something else? Gerv
desktop support is coming as a P2 for Q4 goals. Bug 799671 is the most relevant for this bug I think
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
(In reply to Wil Clouser [:clouserw] from comment #9) > desktop support is coming as a P2 for Q4 goals. Bug 799671 is the most > relevant for this bug I think That's not what this bug is talking about. This is talking about non-firefox browsers. The support was had with the old shim. If that's no longer relevant, then close this as invalid.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee: fligtar → nobody
Status: REOPENED → RESOLVED
Closed: 12 years ago12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.