HTML and CSS Reference
In-Depth Information
transmission from the browser after the URLsomething you can't
do as part of a conventional <a> tag. Passing parameters explicitly
The foregoing bit of advice warrants some explanation. Suppose you
had a simple form with two elements named x and y . The browser en-
codes them like this:
If method=GET , the browser also includes the server-side's processing ap-
plication's URL as a prefix, like this:
There is nothing to keep you from creating a conventional <a> tag that
invokes the form with any parameter value you desire, like so:
<a href="">
The only hitch is that the ampersand that separates the parameters is
also the character-entity insertion character. When placed within the
href attribute of the <a> tag, the ampersand causes the browser to re-
place the characters following it with a corresponding character entity.
To keep this from happening, you must replace the literal ampersand
with its entity equivalent, either &#38; or &amp; (see Appendix F ). With
this substitution, our example of the alternative form reference to the
server-side application looks like this:
<a href=";y=104">
Search WWH ::

Custom Search