Closed Bug 1114911 Opened 10 years ago Closed 5 years ago

Feature Request: Keyboard shortcut for share button.

Categories

(Firefox Graveyard :: SocialAPI, enhancement)

36 Branch
enhancement
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: sin, Unassigned)

References

Details

(Keywords: access)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20141222004004

Steps to reproduce:

Not Applicable.


Actual results:

Not Applicable.


Expected results:

The share button in firefox does not currently have a keyboard shortcut(s) for easy access. It would be much faster and more convenient for a lot of people(say, vim users) if sharing was made possible using only the keyboard. Please consider adding this.
Component: Untriaged → Keyboard Navigation
Keywords: access
Severity: normal → enhancement
Hi Prajjwal, do you any keyboard shortcut in mind? Also, what would you think of navigating between services using arrow keys? :)
Flags: needinfo?(sin)
(In reply to desiradaniel2007 from comment #1)
> Hi Prajjwal, do you any keyboard shortcut in mind? Also, what would you
> think of navigating between services using arrow keys? :)

A modifier plus any letter in the word "share" that isn't already a shortcut for something else would work. From looking at the keyboard shortcuts page for shortcuts of the form (ctrl|alt) + (s|h|a|r|e) that aren't already taken, I'd say the following are good candidates:

* <ctrl> + E
* <alt> + R

Just my opinion, though. Any shortcut would do, as long as it is documented.

I don't think navigating installed services with the arrow keys is a good idea, because people expect the arrow keys to move their cursor in the textarea by default. <alt> + (up|down) doesn't seem to do anything on my firefox. I think that would be the way to go.
Flags: needinfo?(sin)
(In reply to Prajjwal Singh from comment #2)
> * <ctrl> + E

This focuses the search bar on Windows.
Component: Keyboard Navigation → SocialAPI
OS: Linux → All
Hardware: x86_64 → All
Should this follow the lead of bug 1106932?
Flags: needinfo?(philipp)
(In reply to Shane Caraveo (:mixedpuppy) from comment #4)
> Should this follow the lead of bug 1106932?

I think so, yes. That would be great...
I think we should start with having a menu entry / submenus (for share providers that have their own buttons?) under [File]. Finding unused shortcuts is hard, so I think we should defer that for now.

Philipp, it would be great if you could look at this and clarify what should be done here so we can move forward. This kind of stuff is impacting keyboard/accessibility users and shouldn't be too hard to fix as long as we have ideas about how to do so.
Flags: needinfo?(philipp)
(In reply to :Gijs Kruitbosch from comment #6)
> I think we should start with having a menu entry / submenus (for share
> providers that have their own buttons?) under [File]. Finding unused
> shortcuts is hard, so I think we should defer that for now.
> 
> Philipp, it would be great if you could look at this and clarify what should
> be done here so we can move forward. This kind of stuff is impacting
> keyboard/accessibility users and shouldn't be too hard to fix as long as we
> have ideas about how to do so.
Flags: needinfo?(philipp)
Adding Michael and Markus here...

As mentioned elsewhere, the share panel and our task continuity efforts partially solve the same problems. I'd like to have that untangled before proceeding. Whatever the result, keyboard accessibility should be a part of it.
Flags: needinfo?(philipp)
(In reply to Philipp Sackl [:phlsa] please use needinfo from comment #8)
> Adding Michael and Markus here...
> 
> As mentioned elsewhere, the share panel and our task continuity efforts
> partially solve the same problems. I'd like to have that untangled before
> proceeding. Whatever the result, keyboard accessibility should be a part of
> it.

What's the timeline for this? Can we just add a menuitem to open the panel in the meantime? That's relatively low-hanging fruit, and it would at least satisfy the baseline a11y requirements here.
Flags: needinfo?(philipp)
It would be nice to get this addressed in current versions, we have had a partner run into this and bring it up.
(In reply to :Gijs Kruitbosch from comment #9)
> (In reply to Philipp Sackl [:phlsa] please use needinfo from comment #8)
> > Adding Michael and Markus here...
> > 
> > As mentioned elsewhere, the share panel and our task continuity efforts
> > partially solve the same problems. I'd like to have that untangled before
> > proceeding. Whatever the result, keyboard accessibility should be a part of
> > it.
> 
> What's the timeline for this? Can we just add a menuitem to open the panel
> in the meantime? That's relatively low-hanging fruit, and it would at least
> satisfy the baseline a11y requirements here.

There actually is a (sort of) timeline now and it's »as soon as people get off of e10s or as soon as we hire«.
Flags: needinfo?(philipp)
SocialAPI was removed from Firefox 57 and is no longer available in any current release.
Status: UNCONFIRMED → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.