Re: [Erlyaws-list] Unexpected tag behaviour

[Carsten S. <ca...@co...>]

Hi!

Claes Wikstrom schrieb:
> On 5/13/05, Alexander Williams <th...@sp...> wrote:
> 
>>erlyaws-list:
>>
>>  I  was  working  on formatting some Yaws ehtml output to mirror some
>>  already extant HTML used in the nav bar on my station's webpage, and
>>  ended up boggled briefly.
>>
>>  The construct:
>>
>>      {ehtml, [{br}, {br}]}
>>
>>  Will generate:
>>
>>      <br></br><br</br>

Is there a typo here?

>>
>>  Obviously, the resultant layout doesn't look like lines seperated by
>>  a straightforward <br>.
>>
> 
> 
> 
> I think it should, ehtml (tries) to generate xhtml 1.0 compliant output
> and the construct <br> </br> should certainly be the same as <br />

If parsed as HTML, <br></br> is, as I understand it, simply not correct,
as BR is supposed to be empty.  <br /> however is parsed as a BR element
with an extra attribute `/'.

> 
> The only issue I see here is that it's a bit ugly (and verbose) to
> generate <br></br> when <br/> would suffice.
> 
> The plain
> 
> <br>
> 
> statement is old html 4.01 and not correct html anymore.

HTML 4.01 is correct HTML.  XHTML can be made to be nearly correct HTML.

> I still think that any browser which renders <br> </br> different from <br />
> is broken. 

I would agree that this is very surprising.

Take care,

Carsten

-- 
Carsten Schultz (2:38, 33:47)
http://carsten.codimi.de/
PGP/GPG key on the pgp.net key servers,
fingerprint on my home page.