I think standards-compliance is more important here. Just because WordPress has yet to drop UI for deprecated tags doesn't mean that we should be requiring Theme developers to support tags that aren't supported by their chosen doctype.<div>
<br></div><div>It may be reasonable to RECOMMEND that HTML5-doctype Themes retain support for deprecated tags, but I don't think it should be REQUIRED.</div><div><br></div><div>Chip<br><br><div class="gmail_quote">On Sun, Sep 25, 2011 at 1:57 PM, Ian Stewart <span dir="ltr"><<a href="mailto:ian@iandanielstewart.com">ian@iandanielstewart.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">On 2011-09-25, at 8:44 AM, Chip Bennett wrote:<br>
<br>
> The ACRONYM, BIG, STRIKE, and TT tags aren't supported by HTML5. So if you're developing a Theme with the HTML doctype, you don't need to worry about supporting them. Also, for reviewers: if you're reviewing a Theme with the HTML doctype, support of these tags shouldn't be required.<br>
><br>
> I've split these tags out into a separate sub-heading of HTML5-deprecated tags in the Layout Test, to help make this distinction clear. Let me know if you have any other ideas or questions about the Theme Unit Test data.<br>
<br>
</div>I think it makes sense to support deprecated tags with CSS for anything a user can input with the WordPress HTML editor. There's backwards compatibility with older content to worry about and the expectation that users won't know or care about the HTML5 doctype but will care that their content is unstyled.<br>
<br>
Ian<br>
<br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</blockquote></div><br></div>