Ublock: Add keyboard shortcut for opening the Network-Request-Log

Created on 24 Apr 2015  Â·  8Comments  Â·  Source: gorhill/uBlock

Hi, gorhill. I know you're not big on feature requests. But I'm throwing this out there in case you're receptive.

Please add a keyboard shortcut for opening the Network-Request-Log. Something along the lines of CTRL+SHIFT+V or CTRL+SHIFT+U.

Thanks much.

Most helpful comment

@Snapy A lot of "normal" users are on Ff alternatives _because_ of Mozilla regularly re-abandoning their userbase with things like forcing Australis & WebExt. We appreciate @gorhill improving our versions, as well.

All 8 comments

Accel+Shift+U is better, because it won't override the shortcut that some Webmail providers (like GMail and Hotmail) use for "Paste Without Formatting" (I said this in the analogous issue in chrisaljoudi's repo): https://github.com/chrisaljoudi/uBlock/issues/1303

@gorhill @vdcbb You can close the issue now that it has been implemented.

It will be opened again, the shortcuts are not implemented for the non-webext version of uBO for Firefox. I looked into it a bit, it does not appear trivial.

You could add a big warning in the release notes or in the docs. Anyway, "normal" users will be forced by the end of the year to use the webext version. Plus commands is supported since Firefox 48 so users on ESR 52 and uBO webext should be able to use the keyboard shortcuts.

@Snapy A lot of "normal" users are on Ff alternatives _because_ of Mozilla regularly re-abandoning their userbase with things like forcing Australis & WebExt. We appreciate @gorhill improving our versions, as well.

@gorhill Not cool 👎 , whenever and wherever I try to add an "@" sign into any input field/ form (with: cmd+alt+L) it opens the log in a new tab — I don't see any option where/how to change this. I'd be happy if I knew where to change this.

Context: current macOS Sierra with Chrome.

@F-DK I added a note in the _Release notes_ for those who like you feel the need to thumb down because of such issue:

P.S.: Such an issue should never have made it to the release version. The fact that it did means nobody is testing the dev build, or nobody using the dev build reported the issue. It's completely unrealistic to expect me alone to find all such issues. Given the nature of this project, you will have to accept for such quirks to happen when nobody is willing to contribute by using the dev build and reporting such issues. TL;DR: Contribute by installing and using the dev build.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

KonoromiHimaries picture KonoromiHimaries  Â·  3Comments

RoxKilly picture RoxKilly  Â·  4Comments

thebigsmileXD picture thebigsmileXD  Â·  3Comments

GSNord picture GSNord  Â·  3Comments

Travisi picture Travisi  Â·  3Comments