Re: [T5] Unclosed empty HTML tags (bug?)
Gabriel Rodriguez wrote: When Tapestry 5 produces HTML from my TMLs it's removing the / from the end of my empty tags, leaving them unclosed and causing rendering problems on the browser. Is this by design? Is there a setting that needs to be changed? What exactly is your problem, on which tags ? If your problem is linked to unclosed li, br, (so, Tapestry produce HTML 4 compatible markups), and if you want to produce valid XHTML, you will have to set-up Doctype according to http://tapestry.apache.org/tapestry5/guide/templates.html (Template Doctypes ) BUT, you may hit https://issues.apache.org/jira/browse/TAP5-263 and want to look to http://wiki.apache.org/tapestry/Tapestry5HowToXhtml If it's something else, it may actually be a new bug :) Hope it will help, -- Francois Armand Etudes Développements J2EE Groupe Linagora - http://www.linagora.com Tél.: +33 (0)1 58 18 68 28 --- InterLDAP - http://interldap.org FederID - http://www.federid.org/ Open Source identities management and federation - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [T5] Unclosed empty HTML tags (bug?)
The problem is particularly evident with:
link rel=stylesheet href=${style} type=text/css/
The resulting HTML document contains only:
link rel=stylesheet href=${style} type=text/css (no slash!)
I have tried it with no DOCTYPE declaration and with an XHTML 1.0 Strict
declaration and in both cases I get the same result.
I am not using the class CSS annotation because it doesn't meet project
requirements.
Any ideas?
-Original Message-
From: Francois Armand [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2008 8:44 AM
To: Tapestry users
Subject: Re: [T5] Unclosed empty HTML tags (bug?)
Gabriel Rodriguez wrote:
When Tapestry 5 produces HTML from my TMLs it's removing the / from the end
of my empty tags, leaving them unclosed and causing rendering problems on the
browser. Is this by design? Is there a setting that needs to be changed?
What exactly is your problem, on which tags ?
If your problem is linked to unclosed li, br, (so, Tapestry
produce HTML 4 compatible markups), and if you want to produce valid
XHTML, you will have to set-up Doctype according to
http://tapestry.apache.org/tapestry5/guide/templates.html (Template
Doctypes )
BUT, you may hit https://issues.apache.org/jira/browse/TAP5-263 and want
to look to http://wiki.apache.org/tapestry/Tapestry5HowToXhtml
If it's something else, it may actually be a new bug :)
Hope it will help,
--
Francois Armand
Etudes Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
---
InterLDAP - http://interldap.org
FederID - http://www.federid.org/
Open Source identities management and federation
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T5] Unclosed empty HTML tags (bug?)
I've seen a loop iterator around options tags produce the following:
optionvalue
instead of
optionvalue/option
But it only happens only when I try to render the selected attribute
of the option in the loop, something like:
option t:type=loop t:source=x t:value=y
selected=${isSelected}value/option (excuse any typos).
results in:
optionvalue
Francois Armand wrote:
Gabriel Rodriguez wrote:
When Tapestry 5 produces HTML from my TMLs it's removing the / from
the end of my empty tags, leaving them unclosed and causing rendering
problems on the browser. Is this by design? Is there a setting that
needs to be changed?
What exactly is your problem, on which tags ?
If your problem is linked to unclosed li, br, (so, Tapestry
produce HTML 4 compatible markups), and if you want to produce valid
XHTML, you will have to set-up Doctype according to
http://tapestry.apache.org/tapestry5/guide/templates.html (Template
Doctypes )
BUT, you may hit https://issues.apache.org/jira/browse/TAP5-263 and
want to look to http://wiki.apache.org/tapestry/Tapestry5HowToXhtml
If it's something else, it may actually be a new bug :)
Hope it will help,
--
SU3 Analytics Ltd
61b Oxford Gardens
W10 5UJ
London
Tel: +44 20 8960 2634
Mob: +44 75 2501 0825
www.su3analytics.com
SU3 Analytics Ltd is a company registered in England and Wales under company
number 06639473 at registered address 61b Oxford Gardens, London W10 5UJ,
United Kingdom.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [T5] Unclosed empty HTML tags (bug?)
Gabriel Rodriguez wrote:
The problem is particularly evident with:
link rel=stylesheet href=${style} type=text/css/
The resulting HTML document contains only:
link rel=stylesheet href=${style} type=text/css (no slash!)
I have tried it with no DOCTYPE declaration and with an XHTML 1.0 Strict
declaration and in both cases I get the same result.
I think that you have to set the correct content-type for your page, as
describe in the bug report.
But in this case, you will hit the ie bug... So the simplest thing to do
is : vote for the bug, and follow the HowTo.
--
Francois Armand
Etudes Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
---
InterLDAP - http://interldap.org
FederID - http://www.federid.org/
Open Source identities management and federation
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: [T5] Unclosed empty HTML tags (bug?)
Following the Wiki article did the trick! Be sure and do what it says on the
bottom for the latest versions. Don't do the stuff on the top. Thanks!
-Original Message-
From: Francois Armand [mailto:[EMAIL PROTECTED]
Sent: Monday, October 20, 2008 10:03 AM
To: Tapestry users
Subject: Re: [T5] Unclosed empty HTML tags (bug?)
Gabriel Rodriguez wrote:
The problem is particularly evident with:
link rel=stylesheet href=${style} type=text/css/
The resulting HTML document contains only:
link rel=stylesheet href=${style} type=text/css (no slash!)
I have tried it with no DOCTYPE declaration and with an XHTML 1.0 Strict
declaration and in both cases I get the same result.
I think that you have to set the correct content-type for your page, as
describe in the bug report.
But in this case, you will hit the ie bug... So the simplest thing to do
is : vote for the bug, and follow the HowTo.
--
Francois Armand
Etudes Développements J2EE
Groupe Linagora - http://www.linagora.com
Tél.: +33 (0)1 58 18 68 28
---
InterLDAP - http://interldap.org
FederID - http://www.federid.org/
Open Source identities management and federation
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
