Wouter Zoons schrieb:

> Thomas Schapitz wrote:
>
>> Hi there,
>> looking at the messages my mozilla is throwing at the generated HTML
>> (HtmlTidy),
>> I'm wondering what type of HTML this is intended to be?
>>
>> - 4.01 transitional ?
>> - 4.01 strict ?
>> - XHTML 1.0 ?
>>
>> Did you leave out an appropriate declaration intentionally?
>> Might be an interesting feature, to include this into the templates, or
>> better even,
>> to make this configurable via property.
>>
>> Thomas
>>
>>
>
> we used to have that in the template, but we commented it out like you
> can see in /templates/pages/main-layout.jsp.vsl:
>
>
> #if ($xhtml == "true")
> #*
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
>      "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd";>
> *#
> <html:xhtml/>
>
> #else
> #*
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
>         "http://www.w3.org/TR/html4/strict.dtd";>
> *#
>
> #end
>
>
>
> it was breaking cross-browser compatibility, I never fully understood
> way so I removed it (which made it work on all browsers)
>
> play with it until you think you have found a solution, if you let me
> know what to do I'll apply your patch

I just wondered, if the team intended to generate for a certain type.

Without a hint at what compatibility was broken, and for which browsers,
trying to fix this might be difficult for me....

The most notable possible reason is, that it is impossible for any page,
to conform to both declarations at the same time.
The simplest example for this is the <br> <br/> thing:
 - Standard html doesn't know </br> or <br />
 - in XHTML it *has* to be marked as empty <br />

I noted, that andromda is using the <br /> in some of the generated
resources!
(those ending on *.online.help in application-resources.properties.)

The most notable change for browsers, when using a doctype declaration,
is a change
in error treatment: The Browsers are usually much more cheeky with a
declaration.
So it's not sufficient to include the declaration, the generation of the
page has to
change accordingly. (Wich is probably a *lot* of work -
and outside of the andromda scope anyway, because its better left to tag
libraries).

Having no declaration ususally means, that the browsers try to resolve
by guessing.

However, looking at the generated code, this mostly looks like XHTML,
while some browsers assume something close to to HTML 4.01 transitional
or frameset
as default.

Thomas


-------------------------------------------------------
This SF.Net email is sponsored by: New Crystal Reports XI.
Version 11 adds new functionality designed to reduce time involved in
creating, integrating, and deploying reporting solutions. Free runtime info,
new features, or free trial, at: http://www.businessobjects.com/devxi/728
_______________________________________________
Andromda-user mailing list
Andromda-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/andromda-user

Reply via email to