On Tue, Jul 28, 2009 at 5:15 AM, Garrett Smith <g@rre.tt> wrote:
I think that not dealing with this properly is a long term problem.

I agree, which is why I'm trying to keep the discussion open.

We may be close though...

If ehtml provided a 'doctype' element, the rendering engine would have
an explicit direction on how to format the output.

<snip/>

This seems like a pretty nice approach. I've been trying to figure out a nice way of effectively versioning ehtml but without breaking current usage, without duplicating a lot of the ehtml handling code in Yaws, and in a way that's understandable and makes sense, and this idea seems to address all these issues nicely.

I'll take a stab at incorporating this into the changes I've already made, and we'll see how it looks.

thanks,
--steve




On Mon, Jul 27, 2009 at 11:34 PM, Steve Vinoski<vinoski@ieee.org> wrote:
>
>
> On Sat, Jul 25, 2009 at 8:29 PM, Steve Vinoski <vinoski@ieee.org> wrote:
>>
>> Garrett and I had an offline conversation about this because at first I
>> didn't see the issue, but he reminded me that in HTML the input tag
>> officially has no closing tag (sad but true). I don't think it's really a
>> problem in practice, given the huge amount of bad HTML out there that
>> browsers have to compensate for, but we should probably fix this to make
>> Yaws correct in this regard. I'll go ahead and fix it unless someone knows
>> of a good reason not to change it?
>
> Replying to myself, I've gotten some private email stating concerns about
> changing this, primarily because it would disallow the output from being
> treated as XHTML or anything else besides strict HTML 4.01. I think that's a
> valid concern, so perhaps the best course of action really is to just leave
> it alone.
> --steve