Skip to main content
8 events
when toggle format what by license comment
Apr 13, 2017 at 12:37 history edited CommunityBot
replaced http://wordpress.stackexchange.com/ with https://wordpress.stackexchange.com/
Aug 27, 2015 at 10:45 comment added birgire During my testing, I found out that if I skip the wpse.set_keydown_for_tinymce() part, then wpse.set_keydown_for_document() will not catch the ctrl+{p,s} keydown events from the tinymce editor. So that's why I bothered with the tinymce in the first place ;-) If that could be skipped, that would be great @JanBeck
Aug 27, 2015 at 10:18 comment added Jan Beck Thanks for the clarification about your intention to enqueue it as a .js file. I'm still wondering though, why you even care about tinymce at all. Even if your post edit screen only contains a title box wouldn't you still want to be able to save via keyboard shortcut? I guess the question is whether keyboard events happening inside the tinymce are bubbling up into the "outside" post edit screen. Have you tested that?
Aug 27, 2015 at 9:09 history edited birgire CC BY-SA 3.0
added 754 characters in body
Aug 27, 2015 at 9:01 comment added birgire Good question. Since I'm dealing with the tinymce javascript object, then I thought after_wp_tiny_mce would be a handy test-hook for a vanilla install, where I don't expect remove_post_type_support( 'post', 'editor' ) or multiple tinymce editors on a page. But other hooks would work, but we have to make sure tinymce is defined. But we would ship our plugin by enqueue it from a .js file, in the usual way. @JanBeck
Aug 26, 2015 at 21:36 comment added Jan Beck What's the reasoning behind hooking this to tinymce and not to the post edit screen?
Aug 23, 2015 at 1:36 comment added birgire ps: just want to mention that if the page is loaded in Text mode and then switched back to the Visual mode, the tinymce keydown event will not fire.
Aug 22, 2015 at 23:34 history answered birgire CC BY-SA 3.0