Triage: keyboard shortcut

[ianb]

We haven't implemented a keyboard shortcut. For accessibility we may want to (see #2251). If we do, we should find someone that can help us find a keyboard shortcut that won't cause too many problems, as conflicts seem common.

Note there's a metric associated with this, if we don't implement a keyboard shortcut we should update METRICS.md to show it is deprecated; if we do implement it we should use the documented metric.

[wresuolc]

Dolske suggested @gijsk might have a recommendation since he's working on keyboard accessibility

[gijsk]

For the keyboard shortcut to be discoverable you'd need a menuitem, and that'd help inform what screenshot to use. ctrl-shift-s on Windows/Linux and ctrl-opt-s on OSX seem obvious choices, but they're currently used by the devtools debugger. I suppose if we ask nicely maybe the debugger can find a different one; screenshots are arguably useful to more people than the script debugger... I suck at github so I don't know how to ping folks (or maybe github's autocomplete is just broken).

In any case, it would be nice if there was a keyboard equivalent other than the shortcut (ie a menu item, somewhere/somehow).

[garbados]

Hey! I found this mdn tutorial for adding keyboard shortcuts, but I don't know where an HTML solution like that would go in the project. In order to provide the right metrics, I assume a JS component would also be necessary. Where file-wise would those changes go?

[jaredhirsch]

@garbados Hi there! This bug might be a little bit weird, since it's not clear if we can use the WebExtensions APIs, or will have to resort to old-school XUL/restartless addon techniques, like the XUL tutorial you found on MDN. (XUL is an XML-based language which is more like a distant cousin of HTML, and it has a pretty rough learning curve. Probably would be a frustrating experience for someone new to Firefox hacking.) I'd suggest you grab a good first bug instead 👍

@gijsk Hey, thanks for the info. I noticed the commands API gives WebExtensions the ability to register hotkeys. Would that be the right approach here? I don't see any APIs that give WebExtensions the ability to add menu items, so would we need to do that from the embedding restartless addon?

[gijsk]

@gijsk Hey, thanks for the info. I noticed the commands API gives WebExtensions the ability to register hotkeys. Would that be the right approach here? I don't see any APIs that give WebExtensions the ability to add menu items, so would we need to do that from the embedding restartless addon?

I don't know that much about webextensions, actually, so I'm not sure. You could definitely do it from the embedding restartless add-on. Kris or other webextensions folks would be good people to ask.

[ianb]

It wouldn't be as helpful as a menu item under Tools, but we do have a context menu item where we could put the keyboard shortcut, and we could advertise it on the instructions screen.

[gijsk]

I don't think we display shortcuts for context menus. Of course, you could include one in the label but that'll just be ugly.

What we've done elsewhere is include the shortcut in tooltips on buttons (you can try this today on e.g. the downloads button). However, this isn't really sufficient for real keyboard access and accessibility in general - users using screenreaders and other a11y tools generally benefit most from toplevel menuitems (whether that be under Tools or somewhere else).

[ianb]

I've opened #2539 for triage as to whether we should put something in Tools.

[wresuolc]

@johngruen check this out

[johngruen]

@ianb How about ctrl-shift-alt-s / cmnd-shift-opt-s?

[wresuolc]

Marking as needs:ux to identify how to show the keyboard shortcut to users.

[wresuolc]

https://bugzilla.mozilla.org/show_bug.cgi?id=1365757

[ghost]

this is still unsolved. c'mon guys.

[rybarova]

Is it possible to add settings for custom shortcuts? That means a different shortcuts for different users? That would eliminate the problem with conflicts.

[johngruen]

Okay, here's the deal. we want to do this...I'll move it into our product backlog to make sure it gets ranked along with other features.

[abitrolly]

I need to make screenshot of broken html in Firefox extension. Reaching out to menu removes extension popup from the screen, so I am looking for shortcut to capture it.

[step21]

Adding to this, @abitrolly would be great if this could be taken into account, because as far as I understand with these extension popups especially, a keyboard shortcut seems like it should not affect the popup but often will anyway.

[jaredhirsch]

Oh, good catch, @gijsk! I didn't think to look at the accessibility shortcuts.

I'll ping the devtools channel on Monday about that shortcut. I thought it seemed like an odd mnemonic to use Ctrl-Shift-S to open a debugger. It looks like devtools has also taken Ctrl-Shift-D to "cycle between docking modes". I can't imagine either of those shortcuts gets much use, but hopefully there's some Telemetry data that can confirm usage levels.

I'll mark the PR as not ready to merge, for now.

@gijsk, random related question: do you have any idea why the "Keyboard Planning FAQ" page is only available as an archived page, and doesn't seem to live in the current wiki? https://website-archive.mozilla.org/www.mozilla.org/access/access/keyboard/

[gijsk]

I think it's just never been updated. It's wildly out of date when looking at some of the specifics (navigator.dtd, some of the XBL bindings listed), and looks like it was written when the Mozilla Suite (aka SeaMonkey) was more present/important than Firefox (so 2004 or earlier).

[jaredhirsch]

I spoke to @digitarald about devtools keyboard shortcut usage. They don't currently measure which keys are used to open devtools, and Harald helpfully filed https://bugzilla.mozilla.org/show_bug.cgi?id=1456984 to add the keys to the existing ping. It seems like the devtools team might be able to get this landed before 61 goes to beta, so we could have data on Dev Edition usage within a couple of weeks: 61 goes to developer edition on May 7th, and data should be available within a few days to a week after that.

Once the data's been gathered, digitarald will make a decision about whether they want to keep the shortcut, and we'll either use Ctrl + Shift + S, or pick something else.

I'll update this bug as things move along.

[abitrolly]

If there is a chance to make a research, then it is useful to have a table that lists shortcuts for screenshot functions across various operation systems. Like in Fedora I don't need this functionality from FF, because Ctrl+Shift+PrtScr (select area and store in clipboard) covers 80% of what I need. But discovering this is hard. So if Firefox could advise users on systems shortcuts - that would greatly improve user experience and push it outside of the browser.

[jaredhirsch]

@abitrolly All operating systems provide built-in screenshots, but we're not concerned with those in general. Thanks for the suggestion, though.

[ijsnow]

Is there a way to map this action to a browser command? If it were possible, I'd just write a quick browser extension for this instead of waiting for the consensus on what keys to use. I don't care what the keys are I just want to not have to use my mouse :P

[samtuke]

Also hoping for new screenshot shortcuts soon

[arunsathiya]

Dropping by to note my interest for keyboard shortcuts as well. :)

[clouserw]

@6a68 any updates since you talked to @digitarald?

[jaredhirsch]

The Telemetry probes are in Firefox 62, which went to developer edition late in June. I'll ping to see if they have enough data yet to make a decision

[koolamusic]

AAny updates so far ?

[digitarald]

@6a68 with the data from dev-edition we find that shortcut usage for debugger is low enough. I am circling back with the team to see if I missed any trade offs.

[digitarald]

@6a68 👍 from DevTools side.

Only major thing to keep in mind is to update DevTools MDN pages on shortcuts (just by adding dev-docs-needed). Let us know if you need any help with migrating the shortcut to screenshots.

[jaredhirsch]

@digitarald Fantastic! Thanks for the update. I'll add this to the bug list for tomorrow's triage.

[stamster]

Still N/A in latest official FF builds?

[nod5]

@6a68

Note that my PR doesn't add an item to the Tools menu, or add keyboard shortcuts for one-click full-page or save-visible shots. If these things matter to you, please file a new bug 👍

There are plenty of external tools, OS bundled or third-party, to screenshoot area or visible window.
Not so for fullpage screenshot. For that reason add a keyboard shortcut to without any extra steps save a fullpage screenshot to the default download folder.

[ianb]

Closed for #5089, which summarizes the discussion.