User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:25.6) Gecko/20150723 Firefox/31.9 PaleMoon/25.6.0 Build ID: 20150723184543 Steps to reproduce: I use ES File Explorer. I have both Firefox 38 and Firefox Beta 40. But when I try to open a SVG file from ES, it doesn't have a way to open it. It would appear neither version of Firefox is registered as able to open SVG files in Android. You might want to check all the supported file types. Actual results: Firefox doesn't appear to be able to open local SVG files from a file browser. Expected results: File browsers should be able to use Firefox to open SVG files.
If I'm correct (I'm not sure if that's all that has to be done, but on my phone it works), these two lines added in AndroidManifest do the trick.
Comment on attachment 8641748 [details] [diff] [review] bug1188927_svg.diff LGTM, but I want Mike to double check this change.
Comment on attachment 8641748 [details] [diff] [review] bug1188927_svg.diff Review of attachment 8641748 [details] [diff] [review]: ----------------------------------------------------------------- Looks good to me! I haven't done much digging into how we handle opening Intents but because nothing has changed, I'd expect this to just work.
Attachment #8641748 - Flags: review?(michael.l.comella) → review+
Seems like we forgot to actually check this in...
Assignee: nobody → jh+bugzilla
Status: UNCONFIRMED → NEW
Ever confirmed: true
The patch works with ES File Explorer, but not for the internal file manager on Android M, so this needs a little more investigation.
... which is basically bug 1406903, as ES File Explorer uses file://, while the internal file manager uses content://
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/mozilla-inbound/rev/f4946d9cb418 Register Firefox for Android as a handler for SVG files. r=mcomella
https://hg.mozilla.org/integration/mozilla-inbound/rev/f4946d9cb4180e809ccc5587d97caf318e67e818 Bug 1188927 - Register Firefox for Android as a handler for SVG files. r=mcomella
You need to log in before you can comment on or make changes to this bug.