Closed Bug 1270432 Opened 9 years ago Closed 9 years ago

MenuView: add long press actions to MenuItems.

Categories

(Firefox for iOS :: Browser, defect)

Other
iOS
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jhugman, Assigned: jhugman)

References

Details

Attachments

(1 file)

48 bytes, text/x-github-pull-request
fluffyemily
: review+
Details | Review
The menu delegate should should process the long press actions in the same way as for normal actions, i.e. in MenuActionDelegate.
Assignee: nobody → jhugman
Blocks: 1265413
Status: NEW → ASSIGNED
If and when we want to support user re-ordering/removal of menu items within the same menu, this bug will mean we can't use long press to switch into menu edit mode.
Should there be any visual difference to indicate that there is a secondary action behind this menu? (e.g. 'Home…', or a different tint?) Also: note to self: update the HIG docs for MenuView around secondary actions must have a confirmation dialog.
Flags: needinfo?(randersen)
Flags: needinfo?(randersen) → needinfo?(sfranks)
Let's descope the long-press on the home button. A user can still change their home page via settings, and we can spend a little more time thinking on this.
Flags: needinfo?(sfranks)
Attached file Pull request
Added support for MenuItems and MenuToolbarItems.
Attachment #8749593 - Flags: review?(etoop)
I have contradictory thoughts on this, mostly based on a sunk cost fallacy. Do we want to land this anyway and refine it or is it the opportunity cost of using up the long press gesture?
Flags: needinfo?(sfranks)
Comment on attachment 8749593 [details] [review] Pull request LGTM. Just a couple of small things.
Attachment #8749593 - Flags: review?(etoop) → review+
(In reply to James Hugman [:jhugman] [@jhugman] from comment #5) > Do we want to land this anyway and refine it or is it the opportunity cost > of using up the long press gesture? I think it's the latter. If we eventually want users to be able to customize their menus (removing items, rearranging icons) then the natural way to do this on IOS is to long press on an icon to enter this edit mode. Long-pressing the Home button to change the homepage again is also not discoverable, and I also don't believe users will be changing their home pages often enough that a short cut is warranted.
Flags: needinfo?(sfranks)
This is a great reply, thanks. Is there anything to be saved from this PR even if we don't use it in the product? e.g. 3D touch? (:fluffyemily and I have an eye on splitting the menu out as a separate project)
Flags: needinfo?(sfranks)
This is a great reply, thanks. Is there anything to be saved from this PR even if we don't use it in the product? e.g. use a 3D touch gesture? (:fluffyemily and I have an eye on splitting the menu out as a separate project)
Addressed nits, and rebased. Not merged.
Merged though unused by homepage.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Flags: needinfo?(sfranks)
Resolution: --- → FIXED
> Is there anything to be saved from this PR even if we don't use it in the > product? e.g. use a 3D touch gesture? 3D Touch is a great idea. I just reviewed the HIG and no red flags have been raised. We should totally use it for this button to reset the current page as Home. It's a tiny, secret little shortcut, but could be handy. And those without devices that support 3D Touch can still edit their page through the Settings.
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: