- From: Alan J. Flavell <flavell@a5.ph.gla.ac.uk>
- Date: Fri, 5 Nov 1999 10:17:31 +0000 (GMT)
- To: "Neff, Robert" <Robert.Neff@usmint.treas.gov>
- cc: "'w3c-wai-gl@w3.org'" <w3c-wai-gl@w3.org>
On Thu, 4 Nov 1999, Neff, Robert wrote: > SRC="http://path/flashtemplate.swt?type=gif¶m1=val1¶m2=val2 > <http://path/flashtemplate.swt?type=gif¶m1=val1¶m2=val2> " > HEIGHT="111" BORDER="0" WIDTH="222" NATURALSIZEFLAG="1" > ALIGN="BOTTOM" > ALT="Description of the Image" > > Excuse me for butting in with a technical detail that isn't directly relevant to your topic, but both of those attribute values (SRC and HREF resp.) are syntactically invalid HTML. Some browsers will fix up the error by treating the ¶ as a paragraph sign, which makes mincemeat of the attempted aubmission. And HTML validators will very properly report an error. Line 12, character 45: ... h/flashtemplate.swt?type=gif¶m1=val1¶m2=val2 ^ Error: unknown entity param1 Line 12, character 57: ... ate.swt?type=gif¶m1=val1¶m2=val2 ^ Error: unknown entity param2 Ideally, one should use the technique documented in the HTML specificaitons, of using a semi-colon as an alternative delimiter; but of course this only works if the server-side programming has been planned to support both ( '&' for actual form submissions, ';' for URL-created GETs). Should that not be the case, then the correct move is to code the '&' character(s) in the URL, as & (or of course the corresponding & numerical character reference) in the HREF and SRC attributes. (I have a small page discussing this issue, with some actual browser results, at http://ppewww.ph.gla.ac.uk/~flavell/www/formgetbyurl.html ) best regards
Received on Friday, 5 November 1999 05:17:39 UTC