The motivation for adding the accessKey attribute to the button and link widgets is that it is a standard HTML5 feature, and we're just passing the attribute through. (I can't find any references to the attribute being dropped from the standard).
The differences between browsers are sufficiently frustrating that I don't propose to use the accessKey attribute in the core UI. If we want global keyboard shortcuts we'll need to do it properly: a new startup module that listens to key events on the document, reusing the existing keyboard shortcuts pane in the control panel. Best wishes Jeremy -- Jeremy Ruston jer...@jermolene.com https://jermolene.com > On 15 May 2018, at 08:25, PMario <pmari...@gmail.com> wrote: > >> On Tuesday, May 15, 2018 at 3:43:01 AM UTC+2, Mohammad wrote: >> One question, it seems support for accesskey will be dropped for HTML5 >> standard, > > That's not true. TiddlyWiki has keyboard handling functions. But implementing > key-handling libraries is only 20% of the work, that has to be done. ... > JavaScript libraries are only useful for "core" or plugin developers. > > In TiddlyWiki we need the possibility to provide this functionality for > "advanced users" in wikitext, using widgets. > > - We have the keyboard-widget, which allows advanced users to deal with > shortcuts. > see: EditTemplate and several others > - The keyboard-widget maps shortcuts to tiddlywiki actions. using > action-widgets > - and so on. ... > > For most "pages" keyboard handling is simple, because they dispaly "static" > content, with a hand full of input elements. Those pages are created by > developers. The users are "locked in" to be "consumers" and can fill forms, > that sombody else statically defined .... > > In TW we have a highly dynamic UI, that can be modified by "end-users", to be > able to be "content producers". There is no limit how many "forms" (tiddlers > in edit mode) are open at the same time. ... That's a big difference! > >> also different browsers react differently to accesskey, > > It's not only different browsers. .. It's also different OSes that have > sligtly different approaches and implementations. eg: Ctrl-key, Cmd-Key and > Alt-Key .. That's why TW "$:/ControlPanel: Kayboard Shortcuts" tab allows us > to configure every OS separately if needed. > > There are some common shortcuts, everyone knows, that can't be used in > browser-apps, since the browser catches them. No matter what you do! eg: > Ctrl-S, Ctrl-N .... > >> so don't you think a JavaScript solution maybe be a better solution in long >> time? > > That's right. We already use one ... But as I wrote, that's only part of the > game. We need to find ways to make it availalbe for our "wikitext-users", > with consistency and acceptable complexity. > > The proposed pull-request may be only the first step, to get more > flexibility. > > Everyone is welcome to add comments to the discussion. > > have fun! > mario > > > > -- > You received this message because you are subscribed to the Google Groups > "TiddlyWiki" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to tiddlywiki+unsubscr...@googlegroups.com. > To post to this group, send email to tiddlywiki@googlegroups.com. > Visit this group at https://groups.google.com/group/tiddlywiki. > To view this discussion on the web visit > https://groups.google.com/d/msgid/tiddlywiki/22a23cf5-5adb-4b9c-a34c-a9100dc970f7%40googlegroups.com. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to tiddlywiki+unsubscr...@googlegroups.com. To post to this group, send email to tiddlywiki@googlegroups.com. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/ACB9ECCE-19CD-4C09-BB54-DE8C546AE863%40gmail.com. For more options, visit https://groups.google.com/d/optout.
