On Tue, 2008-03-18 at 18:53 +0100, Martin Kersten wrote: > Hi Martin (G.), > > and to recap it would result into & replacements and it would > be interpreted by some browsers correctly and some incorrectly? Hopefully all browsers would interpret & correctly as & when sending the request - as Filip wrote, also referencing http://htmlhelp.com/tools/validator/problems.html#amp
> So <t:outputraw> wont help. I see. Any solution (beside providing > an iframe component). I would like to see a 'raw:' binding or do > I miss something? The solution is that & is totally fine and simply I was wrong when I thought this would end up with & going into the request... So nothing has to be done or changed or anything :) Thanx && cheers, Martin > > Cheers, > > Martin (Kersten) > > > -----Ursprüngliche Nachricht----- > Von: Martin Grotzke [mailto:[EMAIL PROTECTED] > Gesendet: Dienstag, 18. März 2008 18:37 > An: Tapestry users > Betreff: Re: AW: [T5] How to get ampersand (&) rendered raw / not encodedas > &? > > Hi Martin (K.) :) > > just to have this complete, the template part was this: > > <iframe src="http://foo/?foo=bar&${queryString}"; > > with queryString beeing a page property... > > Cheers, > Martin > > > > On Tue, 2008-03-18 at 18:11 +0100, Martin Kersten wrote: > > Hi Martin, > > > > how is the query string is appended? There is always a difference in > > writing text and html. If you write text everything gets converted. If > > you write html (raw) everything will work. > > > > Please just post the tml-part in question. Maybe we can give a shorty for > > it. > > > > > > Cheers, > > > > Martin (Kersten) > > > > > > -----Ursprüngliche Nachricht----- > > Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag > > von Josh Canfield > > Gesendet: Dienstag, 18. März 2008 18:06 > > An: Tapestry users > > Betreff: Re: [T5] How to get ampersand (&) rendered raw / not encoded as > > &? > > > > Hi Martin, > > > > I'm confused by your statement: > > > I would say that a request parameter appended with &param=value > > > would be seen by the server as amp;param instead of just param. > > > > Does this mean that you are seeing a problem on the server side? What you > > are describing is not what I would expect, if you are seeing this then > > there might be something else going on. > > > > Josh > > > > On Tue, Mar 18, 2008 at 7:41 AM, Martin Grotzke <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > On Tue, 2008-03-18 at 14:19 +0100, Chris Lewis wrote: > > > > Martin, > > > > > > > > I'm guessing your mail client converted Josh's message because it > > > > rendered the & in the url as & - just as you have explained > > > > and shown. > > > Ok, thanx :) > > > > > > > As he said, url's with & in place of & are actually correct > > > > and should not cause problems (I personally have never seen these > > > > urls cause any). > > > I would say that a request parameter appended with &param=value > > > would be seen by the server as amp;param instead of just param. > > > > > > Cheers, > > > Martin > > > > > > > > > > > chris > > > > > > > > Martin Grotzke wrote: > > > > > On Mon, 2008-03-17 at 15:24 -0700, Josh Canfield wrote: > > > > > > > > > >> If I am understanding you correctly, you are getting something > > > > >> like this in your source: > > > > >> > > > > >> <iframe src="http://host/page?arg1=val1&arg2=val2";></iframe> > > > > >> > > > > > Nope, unfortunately I get src="http://host/page?arg1=val1&arg2=val2"; > > > > > > > > so the & is rendered as & > > > > > > > > > > Cheers, > > > > > Martin > > > > > > > > > > > > > > > > > > > >> That is actually the correct behavior and it shouldn't be > > > > >> causing a problem in your browser. Are you seeing a problem? > > > > >> > > > > >> http://htmlhelp.com/tools/validator/problems.html#amp > > > > >> > > > > >> Josh > > > > >> > > > > >> > > > > >> On Mon, Mar 17, 2008 at 1:18 PM, Martin Grotzke > > > > >> <[EMAIL PROTECTED]> wrote: > > > > >> > > > > >>> Hi, > > > > >>> > > > > >>> I have a an html element (iframe) that get's a property of my > > > > >>> page class (the current query string) appended to its src attribute. > > > > >>> > > > > >>> The query string may contain the "&" char, which always gets > > > > >>> expanded as "&". Is there any possibility to prevent T5 from > > > > >>> encoding this char? > > > > >>> > > > > >>> Thanx && cheers, > > > > >>> Martin > > > > >>> > > > > >>> > > > > >>> > > > > >>> > > > > >> > > > > >> > > > > > > > > > > > -- > > -- > > TheDailyTube.com. Sign up and get the best new videos on the internet > > delivered fresh to your inbox. > > > > --------------------------------------------------------------------- > > 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] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
signature.asc
Description: This is a digitally signed message part
