<s> and <u> are not obsolete anymore (no-obsolete-elements)
See original GitHub issueAs far as I can tell from the WATWG HTML spec—first link in the referenced documentation—they explain that “Elements in [non-conforming features] list are entirely obsolete, and must not be used by authors” for which the only reference to <s>
is the following:
strike Use
del
instead if the element is marking an edit, otherwise uses
instead.
I have been unable to find any reference to the deprecation of the <s>
element.
Issue Analytics
- State:
- Created a year ago
- Comments:10 (10 by maintainers)
Top Results From Across the Web
Obsolete Definition & Meaning - Merriam-Webster
The meaning of OBSOLETE is no longer in use or no longer useful. How to use obsolete in a sentence. Synonym Discussion of...
Read more >Obsolete Definition & Meaning - Dictionary.com
Obsolete definition, no longer in general use; fallen into disuse: an obsolete expression. See more.
Read more >Errwrap: Go Tool To Wrap and Fix Errors with The New %w ...
Errwrap, Wrap and fix Go errors with the new %w verb directive. This tool analyzes fmt.Errorf() calls and reports calls that contain a...
Read more >14 Obsolete English Words that Deserve Another Chance
Even perfectly good words can die out. But they don't have to stay dead. Enrich your vocabulary with 14 obsolete English words that...
Read more >this application does not have the debuggable attribute ...
this application does not have the debuggable attribute enabled in its manif. 加载中. attribute. https://my.oschina.net/u/1579480/blog/303267.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Like
<i>
and<b>
are not obsolete but repurposed so was<u>
and<s>
. There are semantic reasons to use<u>
and<s>
according to the latest specs¹.For styling purposes yet the developer would and should use CSS but from a pure semantic perspective the above elements provide a different meaning then what they used to have when they were just style presentation tags.
¹
u
spec /s
specThanks for your investigation. It sounds like we can update the rule to match the current deprecated/obsolete elements as I’m assuming that’s what @MelSumner intended with the rule. Although most people would still want to use CSS instead of these particular elements right?