4 ms·
Wow, the second example in fig 111. > <kbd><kbd><samp>File</samp></kbd>|<kbd><samp>Eat Apple...</samp></kbd></kbd> Boy that's terrible. Edit: Oh, I missed th
by jacobmischka 10y ago
Wow, the second example in fig 111.
> <kbd><kbd><samp>File</samp></kbd>|<kbd><samp>Eat Apple...</samp></kbd></kbd>
Boy that's terrible.
Edit: Oh, I missed that the example immediately following it is supposedly equivalent and only uses a single outer tag. I don't really understand then, if they're equivalent then what's the point of the defined semantics above?
- callahad 10y agoMy reading of it is that: 1. <kbd>___</kbd> means "literal user input" 2. <kbd><kbd>___</kbd></kbd> means "this specific, atomic keypress" 3. <kbd><kbd><samp>___</samp></kbd></kbd> means "this specific, atomic button/action/menu item" So you can fall back to just using method 1, but it implies generic user input, inclusive of but not limited to keypresses. Thus, styling and treating a single kbd tag specifically like a keyboard button is still likely incorrect, since that precludes other semantically valid uses?
- egeozcan 10y agoThen I don't understand why didn't they use something like To select all text, press <user-input type="keyboard"> <interaction-group> <interaction type="keypress">Ctrl</interaction> <comment>together with</comment> <interaction type="keypress">A</interaction> </interaction> </user-input> or you can <user-input type="mouse"> <interaction-group> <interaction type="click"> right-click <ui-item>the empty space around the text</ui-item> </interaction> <comment>and</comment> <interaction type="click"> click <ui-item>Select All</ui-item> </interaction> </interaction> </user-input> Nevermind. After writing this now I understand why.