Open Bug 613884 Opened 14 years ago Updated 13 years ago

Introduce custom CSS class for keyboard shortcuts (stop misusing kbd tag)

Categories

(SeaMonkey :: Help Documentation, defect)

Product:
SeaMonkey
Component:
Help Documentation
Type:
defect
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

People

(Reporter: InvisibleSmiley, Unassigned)

Details

From bug 232063 comment 30: > > I suppose opinions of what <kbd> stands for differs, though > > (haven't read the spec) > > http://www.w3.org/TR/html401/struct/text.html#h-9.2.1 says: > "KBD: Indicates text to be entered by the user." Then I guess we should define a class for visual styling of key shortcuts.
HTML5 says: The kbd element represents user input (typically keyboard input, although it may also be used to represent other input, such as voice commands). I guess key shortcuts are also "other input". What do you think Jens?
(In reply to Philip Chee from comment #1) > HTML5 says: > The kbd element represents user input (typically keyboard input, although it > may also be used to represent other input, such as voice commands). > > I guess key shortcuts are also "other input". I'd disagree with that statement as such: keyboard shortcuts are keyboard input, not other input ("voice" was given as an example for the latter). Anyway, the real question is whether we define <kbd> as to be used with *text* keyboard input or *any* keyboard input. HTML5 seems to imply the latter; cf. the examples on the following pages: http://www.w3.org/TR/html5/text-level-semantics.html#the-kbd-element http://www.w3.org/wiki/HTML/Elements/kbd It's news to me that <kbd> can be nested and I'm not sure whether HTML4 states the same. Let's assume it does. Then I'd recommend to do the following: 1. Use <kbd>Hello<kbd> for when the user shall enter "Hello" verbatim, be it using the keyboard, voice, braille or whatever. 2. Use <kbd class="shortcut"><kbd>Shift</kbd>+<kbd>F3</kbd></kbd> style for shortcuts. 3. Define a kbd.shortcut CSS rule accordingly (we can do that later if need be). Deal?
> Deal? I have no stake in this issue. I was just doing some triage and trying to get some bugs resolved one way or another. I just posted some information in case you find it useful. You could perhaps bring it up in m.d.a.seamonkey to get some feedback. The other thing is that I presume we are using the HTML5 parser for our XHTML on trunk.
You need to log in before you can comment on or make changes to this bug.