Closed Bug 5623 Opened 25 years ago Closed 25 years ago

MouseOver and MouseOut events occur inappropirately. (only on bottom edge of image?)

Categories

(Core :: Layout, defect, P3)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: desale, Assigned: joki)

References

()

Details

(Whiteboard: [TESTCASE])

Attachments

(1 file)

Use of <A href="some.html"><someImage height width></A> in HTML is making whole document clickable. onMouseOver, and onMouseOut events are occuring anywhere on whole document. Produnt: Seamonkey. [Apprunner as well as Viewer] Build: 04-27-13. Platform: PC OS: Windows-95. Steps to Reproduce Bug: 1] Please copy the code I am providing, and save as HTML file. 2] Open this HTML file in Viewer as well as apprunner. 3] On upperleft corner you'll see one image of size 50x50. [If you have any image with you can simply change the source of image in code. If you do not have any image, still its fine. You'll see just one square without image which is supposed to be clickable for next link.] 4] You'll see one TextBox call ed "Result Text Box". Which'll show that whether mouseover and mouseout event had been occured or not. 5] You'll see one reset button to reset the textbox. 6] Now after loading the page, move your mouse anywhere inside window. 7] Then take mouse over image, and then takeout mouse from image. 8] Observe the list of events occured in "Result Text Box." Expected Results: Only image area should be clickable, and mouseover and mouseout events should occur only on image area. Actual Results: Whole document is becoming clickable. MouseOver and MouseOut events are occuring all over the document. Code: <html> <head> <title>Test Page</title> </head> <SCRIPT LANGUAGE="JavaScript1.1"> function report(text) { var value=document.workform.result.value; var msg= value+ " " +text; document.workform.result.value=msg; } </SCRIPT> <body > <form name="workform"> <A HREF="some.html" onMouseOver="report('MouseOver()');" onMouseOut="report('MouseOut()');" ><img src="Unknown.jpg" width="50" height="50"></A><br> Result Text Box:<INPUT TYPE=text name="result" size=60><br><br> <input type="reset" value="Reset"> </form> </body> </html>
QA Contact: 4144 → 4616
Assignee: troy → joki
Attached file [TESTCASE] (deleted) —
Whiteboard: [TESTCASE] Seems to work in M7.
I attached the code provided by the reporter as a testcase. I think this bug should be closed as a "WORKSFORME". I tested this today with M7 Apprunner on Windows 98 and there is no problem. I will leave this bug open so the status can be verified on other paltforms.
Summary: Use of <A href="some.html"><Image height width></A> in HTML is making whole document clickable. → MouseOver & MouseOut events occur inappropirately.
Actually I reported this bug and I just tested it again. Seems the problem I explined eirlier is working fine now. The other problem I'm seeing right now is mouseover and mouseout events are not occuring on appropriate events with Win95. Steps to Reproduce: 1] Please copy code provided earlier. Save it as HTML file, and open this file in apprunner. 2] On upperleft corner you'll see one image. Take your mouse over that image. Now take mouse out of image. Expected Resuts: On taking mouse over image, immediately word "MouseOver" should appear in results text box. On taking mouse out of image, immediately word "MouseOut" should appear in results text box. Actual Results: Sometimes "MouseOut" also appears with "MouseOver" on taking mouse over image. Sometimes nothing happens. Changing Summary of bug. I guess in this case it should go to Tom now. Sorry Tom.
OS: Windows 95 → All
Hardware: PC → All
Summary: MouseOver & MouseOut events occur inappropirately. → MouseOver and MouseOut events occur inappropirately. (only on bottom edge of image?)
Whiteboard: [TESTCASE] Seems to work in M7. → [TESTCASE]
Occurrs on latest sun-sparc-solaris nightly build; marking all/all. joki, FWIW bug 7048 is another mouse(over|out) bug for you, which may or may not be of use. See that for more (perhaps unrelated) testcases. Useful bits of info: *it occurs for both constrained and unconstrained images. *it _only_ seems to occur along the bottom of the image *if _only_ occurs if you drag the mouse slowly. I think there's a separate "location of mouse not sampled often enough" bug for that. more redundant testcases, though these nicely have pictures for you (I couldn't reproduce the problem unless it found an actual image): http://techhouse.brown.edu/niq/mozilla/testcases/5623/constrained_img.html http://techhouse.brown.edu/niq/mozilla/testcases/5623/unconstrained_img.html http://techhouse.brown.edu/niq/mozilla/testcases/5623/constrained_debug.html http://techhouse.brown.edu/niq/mozilla/testcases/5623/unconstrained_debug.html The last two just do alerts so you can just load viewer and watch the debugging printouts fly if that's your preference.
The only seeming to occur along the bottom of the image is probably another problem related to things that are outside of their parent boxes - since the parent inline box is only one line of text high.
Looks lie this one also got fixed some how. I just tested this one with todays builds[09-29-09], and everything seems fine now. Marking it fixed.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: