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
The hotkey is bound to "v" at the document level and it doesn't have a namespace. The only simple method of removing it with jQuery appears to be one that ends up unbinding all the jQuery keypress/hotkey events. If there's a better method that doesn't involve "hacky" tactics, I'm all ears. If not, I've found one method that requires me editing jQuery's internal data so I can give the keypress event responsible for the hotkey a namespace for specifically targeting it with unbind.
Hm... Never mind. I was doing this testing through the console, but if we assume the script keeps running before Danbooru's JavaScript does, I actually can add a keypress event listener at the same level (document) for "v" before Danbooru does and use stopPropagation, as I have been, to keep the keypress from reaching Danbooru's event listener.
Then again, a method I could use within parsePost which happens to run after Danbooru's JavaScript would be optimal so the "hacky" method does have a plus side to it. Still open to suggestions. <_<
The hotkey is bound to "v" at the document level and it doesn't have a namespace. The only simple method of removing it with jQuery appears to be one that ends up unbinding all the jQuery keypress/hotkey events. If there's a better method that doesn't involve "hacky" tactics, I'm all ears. If not, I've found one method that requires me editing jQuery's internal data so I can give the keypress event responsible for the hotkey a namespace for specifically targeting it with unbind.
The text was updated successfully, but these errors were encountered: