You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I checked the README, the FAQ, and searched this issue tracker, but couldn't find anything relating to documentation of the passthrough feature.
In fact for several months I was wondering what is the difference between passthrough (Alt-i) and just disabling the extension (Alt-s). Finally, entirely by accident, I found the answer in #656. This is really awesome, because now I understand, I can use Surfingkeys on sites like YouTube! However please document this in the README so that everyone can understand it properly.
The text was updated successfully, but these errors were encountered:
* brookhong/master:
0.9.43 Fixedbrookhong#894 Firefox: Visual mode: Forward/backward document boundary moves viewscreen but not the cursor
Fixedbrookhong#899 Unrecognized key event: Meta-Meta in Firefox
Add settings.caretViewport to limit hints generation on 'v' for entering visual mode
Fixedbrookhong#911 keep scroll position on finding completed
Fixedbrookhong#578 support Emacs keybindings in ACE editor
Fixedbrookhong#907 doesn't work well with TinyMCE editor
Fixedbrookhong#906 pass-through mode is undocumented
* add settings.ignoredFrameHosts for excluding unwanted frames * g# to reload current page without hash fragment
cibinmathew
pushed a commit
to cibinmathew/Surfingkeys-Cibin
that referenced
this issue
Jul 18, 2019
Hi,
I checked the README, the FAQ, and searched this issue tracker, but couldn't find anything relating to documentation of the passthrough feature.
In fact for several months I was wondering what is the difference between passthrough (Alt-i) and just disabling the extension (Alt-s). Finally, entirely by accident, I found the answer in #656. This is really awesome, because now I understand, I can use Surfingkeys on sites like YouTube! However please document this in the README so that everyone can understand it properly.
The text was updated successfully, but these errors were encountered: