| 12:59 pm on Apr 9, 2003 (gmt 0)|
| 1:04 pm on Apr 9, 2003 (gmt 0)|
| 1:18 pm on Apr 9, 2003 (gmt 0)|
unfortunately niether of those work, as the & has to be as an & in the url, not & or %26, as it is submitting to a php page.
i think the solution might be to use JS to insert the character code into the string, but that is what i am not sure how to do.
thanks anyway, donald
| 1:20 pm on Apr 9, 2003 (gmt 0)|
Have you tried replacing the double quotes for single ones?
I thought this might be of interest [w3.org]
Markup Languages Coding Guidelines for Mozilla.org [mozilla.org]
| 3:47 pm on Apr 9, 2003 (gmt 0)|
drnoble, & works fine with my IE6 and Opera7 and is the thing to do according to all the documentation I've seen. One should not feed it to the browsers address bar, though.
Anyway, I've never understood why (x)html validators try to interpret the code inside <script>-tags. None of their business, imho.
| 4:34 pm on Apr 9, 2003 (gmt 0)|
Maybe I'm missing something, but why not define the function in an external .js file? The validator won't see it at all.
| 6:33 pm on Apr 9, 2003 (gmt 0)|
You should always use & for this. The browser should unescape the ampersand and send just an & to the server in the request, and the browser should display just an & on screen. However, in the source code you should be using the full & notation.
| 4:44 pm on Apr 11, 2003 (gmt 0)|
I could put it in an external file, but for a one line script on a sidebar it does not seem worth it.
the solution is either to use html comments (invalid) or to mark it as CDATA
// script here
the answer: [webmasterworld.com...]
which links to: [w3.org...]
| 6:31 pm on Apr 11, 2003 (gmt 0)|
XML-parsers are *required* to look at everything unless specifically told not to.
the correct form is -
I've solved the escape-the-ampersand-problem by going over to ';' instead.
In php you have to change two settings -
arg_separator.output = ";"
arg_separator.input = ";"