> In my defense, since Josh asked, I have actually tried it - but only in a
> browser (by copying and pasting the encoded URL) where such URL wouldn't
> work for me in Chrome (target PHP page would see a variable named "amp;2"
> instead of "2") but when I use an encoded URL in a Tapestry template,
Thiago, Uli, Josh - thank you all. Silly me! Got it now...
In my defense, since Josh asked, I have actually tried it - but only in a
browser (by copying and pasting the encoded URL) where such URL wouldn't
work for me in Chrome (target PHP page would see a variable named "amp;2"
instead of "2") bu
Please go to http://validator.w3.org/ and see for yourself. The & in the URL is
invalid HTML4.01 as
well as invalid XHTML1.0. It has to be encoded as "&".
Uli
On 05.10.2011 16:36, Radoslav Bielik wrote:
> Uli, thank you for your response. I'm confused though. The ampersand is a
> regular element
Did you try it? The browser should do the right thing and decode it before
using the link.
If you use firebug you'll probably see that it's already been unescaped in
the Dom.
On Oct 5, 2011 7:37 AM, "Radoslav Bielik" wrote:
> Uli, thank you for your response. I'm confused though. The ampersand is
On Wed, 05 Oct 2011 11:36:43 -0300, Radoslav Bielik
wrote:
Uli, thank you for your response. I'm confused though. The ampersand is a
regular element of the URL and a separator of 2 querystring variables.
If it was encoded as you suggest, then the target server wouldn't
recognize those as
Uli, thank you for your response. I'm confused though. The ampersand is a
regular element of the URL and a separator of 2 querystring variables. If it
was encoded as you suggest, then the target server wouldn't recognize those
as 2 separate variables (in case of Google Web Fonts those variables are
Uli, thank you for your response. I'm confused though. The ampersand is a
regular element of the URL and a separator of 2 querystring variables. If it
was encoded as you suggest, then the target server wouldn't recognize those
as 2 separate variables (in case of Google Web Fonts those variables are
This is absolutely correct behaviour since the url in the href attribute is not
encoded as it should
be. Replace '&' with '&' and you should be fine.
Uli
On 05.10.2011 16:14, Immutability wrote:
> Hi everyone :)
>
> While playing with Google Web Fonts today http://www.google.com/webfont I
> ran
Hi everyone :)
While playing with Google Web Fonts today http://www.google.com/webfont I
ran into an interesting issue with Tapestry 5.3 (currently running beta 10).
When a possible entity name is encountered by Tapestry within a template
file (TML) even if it resides within an element attribute,
