Closed
Bug 190776
Opened 23 years ago
Closed 23 years ago
serverside imagemap discards static get parameters in target href
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 185169
People
(Reporter: ff-moz, Assigned: asa)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212
Normally (before this version of Mozilla) that meant that:
<a href="page?param=1&hit="><img src="img.png" ismap></a>
could generate uris like this: "page?param=1&hit=?10,10" for a hit at location
10,10, in line with the spec.
According to: http://www.w3.org/TR/html401/struct/objects.html#h-13.6.2
---
The location clicked is passed to the server as follows. The user agent derives
a new URI from the URI specified by the href attribute of the A element, by
appending `?' followed by the x and y coordinates, separated by a comma.
---
However this version of Mozilla strips all get parameters from the href giving
the (incorrect) target of: "page?10,10", given the same code as the example above.
Every other browser (and older versions of mozilla) implement the spec correctly.
Reproducible: Always
Steps to Reproduce:
1. Create a page with a server side image map with parameters in the href.
2. click the imagemap
3. observe that teh parameters given in the href are discarded.
Actual Results:
mozilla generated the uri: page?10,10
Expected Results:
the generated uri should have been: page?param=1&hit=?10,10
This should demonstrate the problem, the param and hit parameter and is stripped
from the href before appending the coordinats:
<a href="page?param=1&hit="><img src="img.png" ismap></a>
Comment 1•23 years ago
|
||
It is exact duplicate of bug 185169.
*** This bug has been marked as a duplicate of 185169 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•