Currently B2G uses the action as the top distinguisher e.g. "open" Android uses the activity as the top element.
Adapting Android's way to do it the example from https://developer.mozilla.org/de/Apps/Manifest#activities "activities": { "share": { "filters": { "type": [ "image/png", "image/gif" ] }, "href": "foo.html", "disposition": "window" } } would become: "activities": { " foo.html ": { "filters": [ { "type": ["image/png","image/gif"], "action": "share" } ], "disposition": "window" } } This would allow different filters to start the same activity foo.html or it would allow different filters to start different activities. My use case would look like this: "activities": { " import.html ": { "filters": [{ "type": ["application/json+foo"], "action": "open" }] }, "openmyurl.html ": { "filters": [{ "type": "url", "url": { "required":true, "regexp": "^mycustomurlscheme:"}, "action": "open" }] } } -Axel -----Original Message----- From: Fabrice Desré [mailto:[email protected]] Sent: Sunday, February 22, 2015 11:38 PM To: Nennker, Axel Cc: [email protected] Subject: Re: [b2g] WebActivities activities filter restrictions On 02/22/2015 07:13 AM, [email protected] wrote: > Frabice, > > Any advice on how to proceed? > In my opinion this use case is not covered by what is expressible in a > manifest. > Is this a b2g thing or more generally a webactivity thing? web activities are pretty much b2g only for now. I'm open to adding support for that if we define a sane manifest format though. Fabrice -- Fabrice Desré b2g team Mozilla Corporation _______________________________________________ dev-b2g mailing list [email protected] https://lists.mozilla.org/listinfo/dev-b2g
