335332 - Imagemapped image moves when clicked, resulting in error

Status: RESOLVED WORKSFORME

(Core :: Layout: Images, Video, and HTML Frames, defect)

Description

[j debert]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

On this page, and others, if an image with an imagemap is not perfectly centered in the browser window, clicking in an imagemap selection area causes the browser to center the image in the window and send the selection it thinks was made _after_ the image has moved. The site returns an error complaining that a selection area was not clicked. The selection areas are small colored squares overlaying the map.

Reproducible: Always

Steps to Reproduce:
1.Got to above url, or another with small imagemapped areas
2.uncenter the image if applicable
3.click on on a small selection area

Actual Results:  
The image jumps to the vertical center of the browser window and the browser sends the coordinates now under the mouse cursor to the server. The server returns an error, saying that no valid selection was made.

Expected Results:  
The image probably should not move and the coordinates actually clicked on should be sent.

Theme and plugins do not affect this problem.

Comment 1

[j debert]

This also occurs for any image which is an anchor for any link.

Comment 2

[Philip Withnall (unavailable)]

I don't understand what you mean by "uncenter the image if applicable". Do you mean use the arrows to move the viewfinder around, or use an extension to dynamically change the CSS to move the whole map box around, or something else?

Comment 3

[j debert]

Revised Steps to Reproduce:
1.Got to above url, or another with small imagemapped areas
2.If image is centered in window, move it off-center vertically. This may  
  require  window to be resized to something smaller than image or the page,
  then scrolling so image is not centered in window.
3.click on on a small selection area

The image will center vertically and apparently will move laterally to some degree. (just discovered, testing). If the window is smaller than the image the window will center itself vertically over the image.

Comment 4

[Philip Withnall (unavailable)]

Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9a1) Gecko/20060425 Minefield/3.0a1 - Build ID: 0000000000
WFM.

Comment 5

[lexual]

Is this still a fault for the user with recent Firefox versions?

Comment 6

[j debert]

(In reply to comment #5)
> Is this still a fault for the user with recent Firefox versions?

This does not occur with Firefox 2.* and Firefox 3.*

Comment 7

[j debert]

Since nothing has been done to resolve this bug and 1.x is effectively obsolete, this bug is marked "resolved:won't fix"

Comment 8

[David Baron :dbaron: (⌚️UTC-5, no longer working on Mozilla)]

The WONTFIX resolution should be reserved for maintainers who decide that a particular bug is something that ought not to be fixed.

In this case, the bug got fixed by something unknown in Firefox 2.*; that means the appropriate resolution is WORKSFORME since we don't know what fixed it.

Comment 9

[j debert]

WONTFIX was selected as the best fit: It was not fixed, no action was taken at all (strongly implying that it will not be fixed) and v1.8 is no longer being maintained or released, so it ought not be fixed. Since the request for clarification, there has been no word from the maintainer(s), except perhaps to see if the same thing occurs in version 2 & 3.

WORKSFORME is misleading: A major version change occurred. Two major version changes have occurred in the interim. The affected component's code or something else was changed for the major version. WORKSFORME says that the bug did not exist, was in error, and so on. 

Perhaps there could be another selection for 'Nothing Was Done", "Forget About It" or such. Or even "No Comment". Even FIXED would work, somewhat, though it would still be a bit misleading.

Comment 10

[j debert]

(Could bug#546557 be somehow related? This bookmark component bug appeared in 3.0 and still exists in 3.5.7 and exhibits somewhat similar behaviour to this bug.)