turning off javascript..
in [JavaScript]
|
Prev: JavaScript code mangler / scrambler / ... khm, more than obfuscator... :)
Next: Simple Ajax question.
From: The Natural Philosopher on 23 Dec 2009 04:56 Thomas 'PointedEars' Lahn wrote: > > No, I did notice that. Your answer was partially wrong anyway (as the > question was completely wrong). > I am not sure how, philosophically speaking, a question can be *wrong*. It may be wildly inappropriate: "How can I eat bananas using pick-axe?" or "Why is Unicorn dung better than cornflakes?" But wrong? No. Wrongness is a property of statements about the truth or otherwise of the stated proposition. Unless you are implying that the question contained an implicit statement that was wrong? Sorry.. Been reading too much metaphsyics recently. :-) > > PointedEars
From: Doug Miller on 23 Dec 2009 07:29 In article <hgsolg$qs5$1(a)news.albasani.net>, The Natural Philosopher <tnp(a)invalid.invalid> wrote: >Doug Miller wrote: >> In article <hgreb8$r8d$1(a)news.albasani.net>, The Natural Philosopher > <tnp(a)invalid.invalid> wrote: >>> Doug Miller wrote: >> >>> I think I dint make myself clear. With js I can fire an evfent handler., >>> set any amount of post variables, and do a submit. I can even submit to >>> a totally different target or spawn a popup window. >>> >>> With strict HTML one button=one vale, >> >> No. The array of POST variables sent to the server includes all named input >> elements in the form, regardless of how many submit buttons there are. >> > >You still misunderstand, the action of pressing the button can only, by >itself, _change_ ONE of them. What? You have multiple <input> elements in a form, and multiple submit buttons. Click *any* of the submit buttons, and the values of *all* of the <input> elements are transmitted to the server. > >Whereas an event handler can set up as many from that one button press >as you care to code for. You don't need an event handler to transmit values from a form to a server. > > >>> and unless I use two forms, one >>> target URL and no spaewning of windows. >>> >>> With a straight URL I can spawn a window, but how to pass variables to >>> it? Except with 'get' >>> Cookies? >> >> Use POST to pass the values to a server-side script which then generates the >> code to spawn the new window. This is trivially easy with PHP. > >? eh? I dont see that. How can I get two windows where only one was >before! the broswer itself is the only entity that can spawn a new windows. Sorry, omitted one thing: target="_blank" attribute in the link.
From: Doug Miller on 23 Dec 2009 07:30 In article <hgsp4t$rk2$1(a)news.albasani.net>, The Natural Philosopher <tnp(a)invalid.invalid> wrote: >Doug Miller wrote: >> In article <hgrehi$rlh$1(a)news.albasani.net>, The Natural Philosopher > <tnp(a)invalid.invalid> wrote: >>> Swifty wrote: >>>> JR wrote: >>>>> But `post` can only be used within a form, I think. >>>> Indeed, but if you *want* the "Submit" button to look like a link, you >>>> can do that simply enough with CSS (I could do it, which is my >>>> definition of "simply enough"). >>>> >>> Problem I have with the submit button, is that if you style it with an >>> image of non square shape, with a transparent edge to it, what shows >>> through is NOT the background image of the containing element, but the >>> plain background COLOR of the containing element. Or possibly the >>> background color of the button itself. Hmm. Perhaps that's the problem. >> >> Perhaps the problem is how you've defined the button.Do you have >> <input type="submit"...> or <input type="image"...> ? > >Input type submit Doug. That'd be the problem then. Try using image instead.
From: JR on 23 Dec 2009 08:39 On Dec 23, 7:51 am, The Natural Philosopher <t...(a)invalid.invalid> wrote: > Thomas 'PointedEars' Lahn wrote: > > Doug Miller wrote: > > >> The Natural Philosopher wrote: > >>> I think I dint make myself clear. With js I can fire an evfent handler., > >>> set any amount of post variables, and do a submit. I can even submit to > >>> a totally different target or spawn a popup window. > > >>> With strict HTML one button=one vale, > >> No. The array of POST variables sent to the server includes all named > >> input elements in the form, regardless of how many submit buttons there > >> are. > > > There is no "array of POST variables". > > Muy Bad, that's how they appear in PHP, of course, but you are perfectly > right. > > The message body of an HTTP POST > > > request is a string, with a HTML form it is usually > > > name1=value1&name2=value2 > > > etc., with names and values URL-encoded. It is only the server-side > > application, e.g. PHP, that makes an (associative) array (e.g., > > $HTTP_POST_VARS or $_POST) out of it. > > Correct, as always, Thomas. ;-) Correct but irrelevant, since anyway you would need a server-side script (PHP, ASP, etc.) to retrieve the data submitted by the client. -- JR
From: JR on 23 Dec 2009 08:48
On Dec 23, 11:39 am, JR <groups_j...(a)yahoo.com.br> wrote: > On Dec 23, 7:51 am, The Natural Philosopher <t...(a)invalid.invalid> > wrote: > > > > > > > Thomas 'PointedEars' Lahn wrote: > > > Doug Miller wrote: > > > >> The Natural Philosopher wrote: > > >>> I think I dint make myself clear. With js I can fire an evfent handler., > > >>> set any amount of post variables, and do a submit. I can even submit to > > >>> a totally different target or spawn a popup window. > > > >>> With strict HTML one button=one vale, > > >> No. The array of POST variables sent to the server includes all named > > >> input elements in the form, regardless of how many submit buttons there > > >> are. > > > > There is no "array of POST variables". > > > Muy Bad, that's how they appear in PHP, of course, but you are perfectly > > right. > > > The message body of an HTTP POST > > > > request is a string, with a HTML form it is usually > > > > name1=value1&name2=value2 > > > > etc., with names and values URL-encoded. It is only the server-side > > > application, e.g. PHP, that makes an (associative) array (e.g., > > > $HTTP_POST_VARS or $_POST) out of it. > > > Correct, as always, Thomas. ;-) > > Correct but irrelevant, since anyway you would need a server-side > script (PHP, ASP, etc.) to retrieve the data submitted by the client. Of course I'm considering that you've told us, from the beginning, that you are "designing the public facing part of a sales website". Therefore, you will need a server-side language and a server database to accomplish that. Cheers, JR |