Support for the HTML elements tt, s, strike and u should be removed. Initially, they should be deprecated in the MW major wiki (Wikipedia, Wiktionary) documentation. Second, they should be replaced on the fly with font-styled spans by the MW engine before reaching the user agent. Third, they should eventually not be supported at all, after wider adoption of HTML5.
Previous discussion on the topic (with new material added at end), centralized here:
- Bug #671 Comment #27 from SMcCandlish <email@example.com> 2008-09-19 21:34:22 UTC ---
We should also be aware that the tt, s, strike, and u elements are also going to be removed from XHTML 2 and HTML 5. The time is probably NOW to start weaning people off of them, though of course they shouldn't simply be deleted from MediaWiki support just yet. It would be good if these were replaced on-the-fly with styled <span>s, though (meanwhile, <i>/'' and <b>/''' should be left alone, as HTML 5 redefines them more narrowly and they will continue to be
- Bug #671 Comment #41 from SMcCandlish <firstname.lastname@example.org> 2010-07-22 01:29:44 UTC ---
[We] will ultimately need to ... get rid of support for the tt element entirely, which doesn't exist in HTML 5. Here's a good discussion of this issue (more broadly than wiki), and Googling about it turns up more:
Ian Hickson, Wednesday, 29 April 2009 6:44 AM:
On Tue, 28 Apr 2009, Jim Garrison wrote:
I am trying to figure out the best way to replace the tt element as I
migrate to HTML5.
Are you using tt to mark up computer code, variables, sample computer
output, user input, for emphasis, to give a span of text in an alternate
voice or mood, a span of text to be stylistically offset from the normal
prose without conveying any extra importance, or something else?
This question must be asked every time a tt element is replaced (manually or
via AWB or whatever), and they WILL need to ultimately be replaced over the next
couple of years.
- Bug #671 Comment #43 here from Aryeh Gregor <Simetricalemail@example.com> 2010-07-22 17:24:10 UTC (In reply to comment #41) ---
[The tt element] exists in HTML5. It's just classified as obsolete
presentational markup, and is not valid
Noted; thanks. HTML5 keeps changing and I stopped trying to track it all quite some time ago. Being mentioned in the standard as *invalid* presentational markup is effectively the same thing as being "not in" the standard, however. And it doesn't change my point about the tt element: The last thing we want is for WP and other wikis' content, whether served by those wikis or repurposed elsewhere, to fail validation out of laziness and cruft. MW's tt still has to go, at least in the long run.
We cannot remove
support for [tt] from MediaWiki without a migration path
to convert all existing markup somehow. But this is a totally separate bug.
No argument from me on either observation. My point is that unless this *is* opened as a bug, it's highly unlikely that any such migration path will be devised (although it would be a near-trivial one anyway; a simple bot could convert these into a styled span, ignoring instances inside pre, nowiki and angle brackets coded as numeric or named character entity references. A new bug for this one should not be set to RESOLVED LATER or no one will do anything to start migrating away from the dead markup.
I would suggest that tt be removed from documentation as "supported", and noted as deprecated with all support for it eventually being removed. For several versions (maybe several years) it should be allowed it in wikicode (i.e., in the editing window and in saved wikicode that editors see in the editing window), but transmogrify it on the fly into a monospaced span before it is served to the user agent. After HTML5 is more fully accepted, tt should just disappear.