Re: [WebDNA] Variable truncating when using javascript openwindow
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107476
interpreted = N
texte = --Apple-Mail-3-1003012127 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii But in that example he is [url]'ing the var's value *twice* just to get = it to work (to not break the URL)... rather than the need for just once, = as we would expect it to work. (?) I popup javascript windows all the time and just wrap the var's vals. = once... (without looking again to be sure I tried with an amp char in = there ;-) >=20 > I'm not sure that your test3 example *is* a hack: that's how it's = supposed to work. When you put text into a URL, it needs to be = URL-encoded for exactly this reason. >=20 > test3 is what I would consider "best practice" rather than "hack" >=20 > On Oct 14, 2011, at 9:31 AM, Steve Raslevich wrote: >=20 >> Thanks for your reply. No, I haven't solved it. For now, I am using = the 'test3' example/hack I listed below. Let me know if you test and = what results you get. I don't think it is anything in the landing page = as using the text link and the hack both display correctly on the = landing page. --Apple-Mail-3-1003012127 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii But = in that example he is [url]'ing the var's value *twice* just to get it = to work (to not break the URL)... rather than the need for just once, as = we would expect it to work.
(?)
I popup = javascript windows all the time and just wrap the var's vals. once... = (without looking again to be sure I tried with an amp char in there = ;-)
I'm not sure that your test3 example *is* a = hack: that's how it's supposed to work. When you put text into a URL, it = needs to be URL-encoded for exactly this = reason.
test3 is what I would consider "best = practice" rather than "hack"
On Oct 14, 2011, at = 9:31 AM, Steve Raslevich wrote:
Thanks for = your reply. No, I haven't solved it. For now, I am using the 'test3' = example/hack I listed below. Let me know if you test and what results = you get. I don't think it is anything in the landing page as using the = text link and the hack both display correctly on the landing = page.
<= /div>
= --Apple-Mail-3-1003012127--
Associated Messages, from the most recent to the oldest:
--Apple-Mail-3-1003012127 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii But in that example he is
[url]'ing the var's value *twice* just to get = it to work (to not break the URL)... rather than the need for just once, = as we would expect it to work. (?) I popup javascript windows all the time and just wrap the var's vals. = once... (without looking again to be sure I tried with an amp char in = there ;-) >=20 > I'm not sure that your test3 example *is* a hack: that's how it's = supposed to work. When you put text into a URL, it needs to be = URL-encoded for exactly this reason. >=20 > test3 is what I would consider "best practice" rather than "hack" >=20 > On Oct 14, 2011, at 9:31 AM, Steve Raslevich wrote: >=20 >> Thanks for your reply. No, I haven't solved it. For now, I am using = the 'test3' example/hack I listed below. Let me know if you test and = what results you get. I don't think it is anything in the landing page = as using the text link and the hack both display correctly on the = landing page. --Apple-Mail-3-1003012127 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii But = in that example he is
[url]'ing the var's value *twice* just to get it = to work (to not break the URL)... rather than the need for just once, as = we would expect it to work.
(?)
I popup = javascript windows all the time and just wrap the var's vals. once... = (without looking again to be sure I tried with an amp char in there = ;-)