{html_* not standards compliant

[GoogleCodeExporter]

The output of the {html_*} plugins render the output to xhtml and not html.

For example I use <doctype html4/strict.dtd> so it aslways sauses a
validation error as the tabs end up as 
<input type="checkbox"/>
instead of
<input type="checkbox"/>

What I suggest it creating a new set called {xhtml_*} and change the
{html_*} to being strict.

Original issue reported on code.google.com by pedromor...@gmail.com on 20 Feb 2008 at 3:19

[GoogleCodeExporter]

Original comment by pedromor...@gmail.com on 20 Feb 2008 at 3:20

• Added labels: Priority-Low, Usability
• Removed labels: Priority-Medium

[GoogleCodeExporter]

Those two examples are exactly the same. Did you mean to say that it always 
ends up
as <input type="checkbox"/> instead of <input type="checkbox">?

Original comment by lorderunion on 28 Mar 2008 at 9:16

[GoogleCodeExporter]

Doh... yes!

And the same for some of the other element also.

It wont break backwards compat if they are changes and the new ones in {xhtml_*
namespace}.

But this is me being a standards purist. And have the modifiers available 
already ;-)

Original comment by pedromor...@gmail.com on 28 Mar 2008 at 10:49

[GoogleCodeExporter]

I wonder if this is still relevant in the age of HTML5?!

Original comment by rodneyrehm on 27 Sep 2011 at 3:18

[GoogleCodeExporter]

Yes it is still relevant. Almost nobody uses XHTML these days, mostly because 
your pages will not even load in Internet Explorer (IE shows a popup asking you 
what to do with the file).

Original comment by martijn...@gmail.com on 16 Dec 2011 at 7:45

[GoogleCodeExporter]

I think quite a lot of people use xhtml served as html. xhtml's stricter syntax 
makes for cleaner code.
Rather than multiplying the code by making different plugin versions for 
different doctypes, I think a better route would be able to specify a target 
doctype (or at least doctype class, e.g. html or xhtml) as a smarty property. 
That value would be visible to plugins via the instance they receive, and they 
would thus be able to change their rendering to match the target doctype.
I know smarty can be used for rendering things other than HTML, however, I 
doubt you'd use an HTML select generator in a non-html context, and the doctype 
can just be ignored.

Original comment by marcus.b...@gmail.com on 2 Mar 2012 at 9:21