Closed Bug 300784 Opened 19 years ago Closed 18 years ago

DOMParser().parseFromString causes mouseout events to get lost

Categories

(Core :: DOM: Events, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jirkaster, Unassigned)

References

()

Details

(Keywords: regression, testcase)

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b3) Gecko/20050713 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b3) Gecko/20050713 Firefox/1.0+

In the page at http://dgs.xhosting.cz/, javascript tooltips are sometimes shown
double with nigthly Deer Park builds -- there should be shown once.

Mozilla Firefox 1.0.4, Opera 8.01 and MSIE 6.0 SP1 on Windows 2000 show them
correctly.

Reproducible: Sometimes

Steps to Reproduce:
1. Move the mouse-cursor on links in the right sidebar.

Actual Results:  
Javascript tooltips are sometimes shown double.

Expected Results:  
Javascript tooltips should be shown once.
Mozilla/5.0 (X11; U; Linux i686; cs-CZ; rv:1.7.6) Gecko/20050524 Firefox/1.0
(Ubuntu package 1.0.2 MFSA2005-44)
Correctly.

It seems only trunk (Gecko 1.8.x) versions are affected.
Flags: blocking1.9a1?
Flags: blocking1.8b5?
Can anyone confirm existence on branch?
Flags: blocking1.8b5? → blocking1.8b5-
(In reply to comment #3)
> Can anyone confirm existence on branch?

I can confirm this bug on Firefox 1.5 beta 2.
Flags: blocking1.8rc1?
I can't reproduce this with the latest branch nightly build on windows. Bob or
Jesse, do you see anything obvious here that would suggest a more widespread
problem?
With Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.9a1)
Gecko/20051011 Firefox/1.6a1, I can reproduce the bug about 20% of the time by
following these steps:

1. Load http://dgs.xhosting.cz/
2. Put the mouse over one of the names on the right.
3. Move the mouse down two items.

I think the reason this bug is difficult (at least on this page) is that it is
timing-dependant.

My initial guess is that Firefox is firing onmouseover events that
http://dgs.xhosting.cz/wp-content/plugins/fancytooltips/fancytooltips.js doesn't
expect.  I can try to make a simplified testcase if you want.
Keywords: regression
I won't be able to look at this again (to try to make a reduced testcase) until
Monday or Tuesday.
Flags: blocking1.8rc1? → blocking1.8rc1-
Attached file testcase β€”
When quickly hovering over the red lines, you should only see the number 0 or 1 as result.
There seem to be 2 regressions:
Between  2004-06-18 and 2004-06-22. Before, it would display 0 or 1, which is good. After that the number is slowly becoming more negative (meaning that mouseout events seem to fire too often here).
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2004-06-18+08&maxdate=2004-06-22+10&cvsroot=%2Fcvsroot
My guess would be because of bug 20022.

And between 2005-03-28 and 2005-03-29. After 2005-03-29, the number is slowly becoming more positive (meaning that mouseout events are probably getting lost here).
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-03-28+08&maxdate=2005-03-29+08&cvsroot=%2Fcvsroot
I think bug 284664 might be the culprit here.
Assignee: nobody → events
Blocks: 284664
Status: UNCONFIRMED → NEW
Component: General → DOM: Events
Ever confirmed: true
Keywords: testcase
Product: Firefox → Core
QA Contact: general → ian
Version: unspecified → Trunk
The DOMParser().parseFromString code in the testcase (which isn't doing anything useful further) is causing the issue.
Summary: javascript tooltips are shown double → DOMParser().parseFromString causes mouseout events to get lost
Is this still reproducable in current trunk builds?
Flags: blocking1.9a1? → blocking1.9-
Whiteboard: [wanted-1.9]
(In reply to comment #10)
> Is this still reproducable in current trunk builds?

No, the testcase is wfm with current trunk builds.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
Flags: wanted1.9+
Whiteboard: [wanted-1.9]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: