Closed
Bug 769454
Opened 13 years ago
Closed 13 years ago
Move HelperApps to context menus
Categories
(Firefox for Android Graveyard :: General, defect)
Firefox for Android Graveyard
General
Tracking
(firefox16 verified)
RESOLVED
FIXED
Firefox 16
Tracking | Status | |
---|---|---|
firefox16 | --- | verified |
People
(Reporter: wesj, Assigned: wesj)
References
Details
(Keywords: ux-discovery)
Attachments
(2 files, 3 obsolete files)
2.36 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
4.99 KB,
patch
|
mfinkle
:
review+
|
Details | Diff | Splinter Review |
Our current helper apps implementation is a bit heavy weight. As a first step to undo that, let's not show a doorhanger, but instead just add a context menu item. When the user long taps on a link that can open in a (non browser) HelperApp, we'll add something like "Open in YouTube App" or "Open in App" when there is more than one choice.
Assignee | ||
Comment 1•13 years ago
|
||
And back in the YouTube hack goes. This isn't perfect. For instance, on YouTube we end up redirecting (twice) from a link. So long tapping on the link to the m.youtube.com won't give the "Open in App" option. But it works for Maps links on Yelp, which is my other use case.
Changing the context menu option to include the App name would be nice follow up. I could hack it here, but would rather fix up the contextmenu API to allow dynamic names instead.
Assignee: nobody → wjohnston
Attachment #637723 -
Flags: review?(mark.finkle)
Comment 2•13 years ago
|
||
Comment on attachment 637723 [details] [diff] [review]
Patch
This isn't too bad, but I think we need the name of the helper app. Can we remove/re-add the context menu? Or maybe only add the menu when we need it?
Comment 3•13 years ago
|
||
Also, maybe we should backout/disable the current behavior while this is addressed.
Assignee | ||
Comment 4•13 years ago
|
||
I'll split this up into two parts to remove the current behavior.
Adding dynamically isn't exactly possible with the current behavior.... maybe we can listen for the context menu event sent to the page and add the listener there. We'd have might also have to fire some notification when the prompt goes away...
Thats just too hacky. I'll add dynamic context menu titles instead I think. How nervous are you about changing the current NativeWindow API's?
Assignee | ||
Comment 5•13 years ago
|
||
Backout the doorhanger. Leave in HelperApps.js for later.
Assuming this is ok with you, I'm PTO today and someone else will have to land.
Attachment #637723 -
Attachment is obsolete: true
Attachment #637723 -
Flags: review?(mark.finkle)
Attachment #639397 -
Flags: review?(mark.finkle)
Comment 6•13 years ago
|
||
(In reply to Wesley Johnston (:wesj) from comment #4)
> I'll split this up into two parts to remove the current behavior.
>
> Adding dynamically isn't exactly possible with the current behavior....
> maybe we can listen for the context menu event sent to the page and add the
> listener there. We'd have might also have to fire some notification when the
> prompt goes away...
>
>
> Thats just too hacky. I'll add dynamic context menu titles instead I think.
> How nervous are you about changing the current NativeWindow API's?
Adding methods is fine. What other changes are you thinking about
Updated•13 years ago
|
Attachment #639397 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 7•13 years ago
|
||
Assignee: wjohnston → nobody
Assignee | ||
Updated•13 years ago
|
Whiteboard: [leave open]
Assignee | ||
Comment 8•13 years ago
|
||
This uses an object with a toString() method to create a dynamic title for this entry. It depends on contextmenu code calling us in a particular order (call filter, if that works, get the name).
Assignee: nobody → wjohnston
Attachment #640315 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 9•13 years ago
|
||
Alternative approach, allows passing a function for the contextmenuitem's (is that one word or three?) name.
Attachment #640315 -
Attachment is obsolete: true
Attachment #640315 -
Flags: review?(mark.finkle)
Attachment #640463 -
Flags: review?(mark.finkle)
Assignee | ||
Comment 10•13 years ago
|
||
Whoops. Tiny tweak I forgot to qref
Attachment #640463 -
Attachment is obsolete: true
Attachment #640463 -
Flags: review?(mark.finkle)
Attachment #640464 -
Flags: review?(mark.finkle)
Comment 11•13 years ago
|
||
Comment 12•13 years ago
|
||
Comment on attachment 640464 [details] [diff] [review]
Patch
>diff --git a/mobile/android/locales/en-US/chrome/browser.properties b/mobile/android/locales/en-US/chrome/browser.properties
>+helperapps.openWithList2=Open With App
is "Open With an App" a little better?
And we should update the document here to add support for the "function" version of "name"
https://developer.mozilla.org/en/Extensions/Mobile/API/NativeWindow/contextmenus
Attachment #640464 -
Flags: review?(mark.finkle) → review+
Assignee | ||
Comment 13•13 years ago
|
||
https://hg.mozilla.org/integration/mozilla-inbound/rev/391f4f60d810
Updated the string. Updating the docs...
Assignee | ||
Updated•13 years ago
|
Whiteboard: [leave open]
Assignee | ||
Comment 14•13 years ago
|
||
Comment 15•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 16
Comment 16•13 years ago
|
||
Is this going to Aurora?
Verified Fixed on trunk (07/11)
Discoverability is kind of tough on this. Who would long-tap on a link?
status-firefox16:
--- → verified
Updated•13 years ago
|
Keywords: ux-discovery
Assignee | ||
Comment 17•13 years ago
|
||
(In reply to Aaron Train [:aaronmt] from comment #16)
> Discoverability is kind of tough on this. Who would long-tap on a link?
I don't think long tap on a link is that uncommon. Every mobile browser I know of has it. BUT I think the goal here was to have the option when its needed, but overall we want to keep people in the browser. i.e. I don't think we want this to be TOO discoverable.
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•