= Description =

STRIKE, S, and U are deprecated in HTML 4.01, and gives validation error
when validating as HTML Strict.

== Steps to reproduce ==

Add overstriked text, and validate.

== Example ==

See MoinMoinFeatures for an example.

##Add URL that show the bug, screenshot or test wiki markup that fail...

##URL: 

##attachment:screenshot.png

##{{{
##Example wiki markup that fail
##}}}

== Details ==

## If you got a traceback, please save the traceback page as html and attach here:
## attachment:traceback.html

## if the bug is in this wiki, just kill the table and write: This Wiki.

## If a traceback is not available, please fill in the details here:
|| '''!MoinMoin Version''' ||  ||
|| '''OS and Version''' ||  ||
|| '''Python Version''' ||  ||
|| '''Server Setup''' || ||
|| '''Server Details''' || ||


== Workaround ==
## How to deal with the bug until it is fixed


= Discussion =

This will be fixed as part of this larger patch: MoinMoinPatch/FormatterApiConsistencyForHtmlAttributes -- DeronMeranda <<DateTime(2006-01-18T17:47:06Z)>>

 I think those tags are being removed from HTML for a reason. Is it wise to put them into MoinMoin (and even keep adding more)? -- RadomirDopieralski <<DateTime(2006-01-18T18:52:33Z)>>

   The elements such as {{{<strike>}}} are currently ''deprecated'', which means that are technically still in the standard--but it serves as warning that new revisions of the standard may remove them.  In this case they are being deprecated because their behavior and semantic meaning can be completely replaced with CSS.  So the ability to display text that is striked-out is not going away, just the particular use of {{{<strike>}}} to accomplish that.  Also from what I can tell, only {{{<strike>}}} was still being used by moin; {{{<s>}}} and {{{<u>}}} were not (unless you can point me to some part of the code that does).  The other patch I mentioned is using {{{<span>}}} instead with CSS classes. -- DeronMeranda <<DateTime(2006-01-18T21:18:00Z)>>

I suggest just to use the `del` element instead, which is conforming to the HTML "strict" standard, and semantically more meaningfull than `strike` (''deleted'' = logial vs. ''strike through'' = optical markup). -- MartinBayer <<DateTime(2006-01-20T00:14:09Z)>>

   Perhaps, but I'm leaning toward keeping it styled only.  The {{{<del>}}} element is actually intended to carry quite a bit of semantic information that {{{<strike>}}} does not; and I'm not sure that the intent of the {{{--(strike)--}}} markup was to carry that meaning.  This fix was simply to replace the deprecated element with the equivalent CSS (as the HTML spec says to do).  The {{{<del>}}} and its companion {{{<ins>}}} may perhaps be useful in some circumstances; but they do not have any standardized visual appearance, and in fact the standard says that browsers may want to not render content inside a {{{<del>}}} at all--so it's not necessarily a good replacement for {{{<strike>}}}.  Furthermore their usefulness comes in when you can provide a {{{cite}}} or {{{title}}} attribute.  It seems to me those are best for something like showing the differences between two revisions of a page (as an alternative to the "diff" display now). -- DeronMeranda <<DateTime(2006-01-20T15:28:44Z)>>

= Plan =
## This part is for Moin``Moin developers:

 * Priority: 
 * Assigned to:
 * Status: fixed in refactor branch using span / css classes

----
## If you are a moin core developer, replace the category to Category* in these cases:
## Category MoinMoinNoBug - if this is not a bug.
## Category MoinMoinBugConfirmed - if you can confirm the bug on current code.
## Category MoinMoinBugFixed - after the bug is fixed in current code.
CategoryMoinMoinBugFixed