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. 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).
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 >>> >>> >>> >>> >> >>
