Re: [WebDNA] Variable truncating when using javascript openwindow
This WebDNA talk-list message is from 2011
It keeps the original formatting.
numero = 107478
interpreted = N
texte = --Apple-Mail=_1C87D8FF-EBE6-48E0-9C43-83D26C8A4E29Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiJavascript (acting on behalf of the browser) will interpret a URL =encoded string on its own before passing onto the landing page. If =you're using popups or redirects with JS, you have to think of it as =sending a parameter twice (unlike a standard link). Thus, wrapping the =variable with [url] twiceOn Oct 14, 2011, at 1:17 PM, Govinda wrote:> 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.> (?)>=20> 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>>=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.>=20> --------------------------------------------------------- This message =is sent to you because you are subscribed to the mailing list . To =unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us--Apple-Mail=_1C87D8FF-EBE6-48E0-9C43-83D26C8A4E29Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-ascii
Javascript (acting on behalf of the browser) will interpret a URL =encoded string on its own before passing onto the landing page. If =you're using popups or redirects with JS, you have to think of it as =sending a parameter twice (unlike a standard link). Thus, wrapping =the variable with [url] twice
On Oct =14, 2011, at 1:17 PM, Govinda wrote:
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>
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list
.To unsubscribe, E-mail to: archives: http://mail.webdna.us/l=ist/talk@webdna.usBug Reporting: support@webdna.us
=--Apple-Mail=_1C87D8FF-EBE6-48E0-9C43-83D26C8A4E29--
Associated Messages, from the most recent to the oldest:
--Apple-Mail=_1C87D8FF-EBE6-48E0-9C43-83D26C8A4E29Content-Transfer-Encoding: quoted-printableContent-Type: text/plain;charset=us-asciiJavascript (acting on behalf of the browser) will interpret a URL =encoded string on its own before passing onto the landing page. If =you're using popups or redirects with JS, you have to think of it as =sending a parameter twice (unlike a standard link). Thus, wrapping the =variable with
[url] twiceOn Oct 14, 2011, at 1:17 PM, Govinda wrote:> 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.> (?)>=20> 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>>=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.>=20> --------------------------------------------------------- This message =is sent to you because you are subscribed to the mailing list . To =unsubscribe, E-mail to: archives: =http://mail.webdna.us/list/talk@webdna.us Bug Reporting: =support@webdna.us--Apple-Mail=_1C87D8FF-EBE6-48E0-9C43-83D26C8A4E29Content-Transfer-Encoding: quoted-printableContent-Type: text/html;charset=us-ascii
Javascript (acting on behalf of the browser) will interpret a URL =encoded string on its own before passing onto the landing page. If =you're using popups or redirects with JS, you have to think of it as =sending a parameter twice (unlike a standard link). Thus, wrapping =the variable with
[url] twice
On Oct =14, 2011, at 1:17 PM, Govinda wrote:
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>
---------------------------------------------------------This message is sent to you because you are subscribed tothe mailing list
.To unsubscribe, E-mail to: archives: http://mail.webdna.us/l=ist/talk@webdna.usBug Reporting: support@webdna.us
=--Apple-Mail=_1C87D8FF-EBE6-48E0-9C43-83D26C8A4E29--
aaronmichaelmusic@gmail.com
DOWNLOAD WEBDNA NOW!
Top Articles:
Talk List
The WebDNA community talk-list is the best place to get some help: several hundred extremely proficient programmers with an excellent knowledge of WebDNA and an excellent spirit will deliver all the tips and tricks you can imagine...
Related Readings:
WC2.0 Memory Requirements (1997)
convertchars and e-mail (1998)
2nd WebCatalog2 Feature Request (1996)
Populating a db from a form textarea (2005)
Download URL & access on the fly ? (1997)
How can I Add several Items into the cart at once? (1997)
New Mac Public Beta Available (1997)
2.0 Info (1997)
[Fileinfo] Context (2000)
What folder??? (1999)
WebCommerce: Folder organization ? (1997)
showif comparison begins w/ and contains (1997)
New public beta available (1997)
payflowpro broken on WebDNA 5.1? (2003)
Signal Raised Error (1997)
Requiring that certain fields be completed (1997)
[CART] (1997)
OT-JS why it does not run on Mac (2001)
WebCat/Typhoon Status under Windows (1998)
formula part 3 (2000)