[rfc-i] <tt> vs HTML5
julian.reschke at gmx.de (Julian Reschke) Sat, 20 February 2016 10:48 UTC
From: julian.reschke at gmx.de (Julian Reschke)
Date: Sat, 20 Feb 2016 11:48:36 +0100
Subject: [rfc-i] <tt> vs HTML5
Message-ID: <56C84484.2000902@gmx.de>
<https://tools.ietf.org/html/draft-iab-html-rfc-02#section-9.63>: > 9.63. <tt> > > This element is directly rendered as its HTML counterpart. but <https://www.w3.org/TR/html5/obsolete.html#non-conforming-features>: > basefont > big > blink > center > font > marquee > multicol > nobr > spacer > tt > > Use appropriate elements or CSS instead. > > Where the tt element would have been used for marking up keyboard input, consider the kbd element; for variables, consider the var element; for computer code, consider the code element; and for computer output, consider the samp element. > > Similarly, if the big element is being used to denote a heading, consider using the h1 element; if it is being used for marking up important passages, consider the strong element; and if it is being used for highlighting text for reference purposes, consider the mark element. > > See also the text-level semantics usage summary for more suggestions with examples. So that's a requirement to produce invalid HTML... Best regards, Julian
- [rfc-i] <tt> vs HTML5 Julian Reschke
- [rfc-i] <tt> vs HTML5 Carsten Bormann
- [rfc-i] <tt> vs HTML5 Riccardo Bernardini
- [rfc-i] <tt> vs HTML5 Paul Hoffman
- [rfc-i] <tt> vs HTML5 Julian Reschke
- [rfc-i] <tt> vs HTML5 Paul Hoffman
- [rfc-i] <tt> vs HTML5 Carsten Bormann
- [rfc-i] <tt> vs HTML5 Julian Reschke
- [rfc-i] <tt> vs HTML5 Paul Hoffman
- [rfc-i] <tt> vs HTML5 Julian Reschke
- [rfc-i] <tt> vs HTML5 Brian E Carpenter
- [rfc-i] <tt> vs HTML5 Joe Hildebrand jhildebr
- [rfc-i] <tt> vs HTML5 Paul Hoffman
- [rfc-i] <tt> vs HTML5 Julian Reschke