View Edit Attributes History Attach Print Search | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Menu | PmWiki / AccessKeys | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Menu
Options |
visitors (intermediate)
Access keys (See also Wikipedia:access keys) are keyboard shortcuts for tasks that would otherwise require a mouse click. They are part of markup that may exist on any webpage. On PmWiki steps have been taken to make it easier to use access keys throughout a site, and to make it possible to adjust key assignments to accommodate different languages and preferences. Using access keys in different operating systems and browsersAccess keys require you to hold down two or more keys.
Exceptions exist for specific browsers, and specific versions. For example,
Note, in cases of conflicts between the keyboard shortcuts assigned by browsers and access keys assigned by links and other markup on webpages, many browsers, including Mozilla, Netscape and Internet Explorer, allow access keys to override the browser defaults and require a different sequence to continue using overridden browser assignments (typically, by pressing and releasing the Alt key, instead of holding it down). Access key assignments in this PmWiki installationThe following is a list of the currently defined access keys for built-in actions. Remember that the letters identified below must be used together with the combination listed above (depending on your operating system and browser). Note that some actions do not have a corresponding access key by default.
Note: If the 'Key Value' is the same as the 'Key Name', the access key is currently undefined. When can these access keys be used
Following table explains which button is activated by which access key. Note that the Cancel button has no access key.
admins (intermediate) Customizing access keysPmWiki uses the same "phrase translation" methods for access key mappings as it does for internationalization. This makes it possible for administrators, skins, language translators, and visitors to all influence the way that specific keys are mapped to actions. See SitePreferences and Site.Preferences for more information and a template. Note that some skins (e.g., Lean) don't use the translation mechanism. In this case one must edit the template file itself in order to change the access keys. By convention, the translation phrases for all of the access key actions start with the characters "ak_", so that the page variable " Implementation of access keysAccess keys are implemented in html as optional parameters that can be added to links and many other types of markup. Example: The list of access key assignments in default PmWiki installations generally work throughout a site because links have been created in PmWiki skins and editing screens that incorporate access key parameters using the access key translation phrases. One location where those links can be viewed is Site.PageActions. That page contains the links that the default PmWiki skin, and many other skins, use to generate links such as "View" "Edit" and "History" that appear on most pages (other than editing screens). Each of the links in that page also has an This page may have a more recent version on pmwiki.org: PmWiki:AccessKeys, and a talk page: PmWiki:AccessKeys-Talk. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
View Edit Attributes History Attach Print Search Page last modified on March 31, 2016, at 04:38 PM |