You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, ~~foo~~ in wikitext renders to HTML <strike>foo</strike>
Describe the solution you'd like
Change it to <s>
Describe alternatives you've considered None
Additional context
Other inline markup (from the first table here) is rendered to the same HTML by wikitext and Markdown. Only differences I could tell briefly are: Markdown renders s for strikethrough, and doesn't support highlight and underline. Regardless of semantics or specs, this should be changed for consistency, to bring the output of both types closer (better for testing, styling, and consuming TW output).
Wikitext already favours other semantic tags (strong instead of b, em instead of i) since 10+ years (?)
Hi @jn64@pmario backwards compatibility is indeed the problem here. It would not be reasonable to break existing CSS rules that are in use in the field. I agree that it is jarring that we use an old school HTML element, but the HTML backwards compatibility guarantees are intended for exactly these kind of scenarios, and provide protection that nothing is going to break with the status quo.
Is your feature request related to a problem? Please describe.
Currently,
~~foo~~
in wikitext renders to HTML<strike>foo</strike>
Describe the solution you'd like
Change it to
<s>
Describe alternatives you've considered
NoneAdditional context
Other inline markup (from the first table here) is rendered to the same HTML by wikitext and Markdown. Only differences I could tell briefly are: Markdown renders
s
for strikethrough, and doesn't supporthighlight
andunderline
. Regardless of semantics or specs, this should be changed for consistency, to bring the output of both types closer (better for testing, styling, and consuming TW output).Wikitext already favours other semantic tags (
strong
instead ofb
,em
instead ofi
) since 10+ years (?)Browser support for both elements is the same (everyone has supported both for as long as anyone knows):
https://caniuse.com/mdn-html_elements_s
https://caniuse.com/mdn-html_elements_strike
strike
is obsoleted inHTML5the HTML Living Standard. Both were deprecated in HTML 4.0 and we kept using them, so this is the least important reason.The text was updated successfully, but these errors were encountered: