Closed Bug 715999 Opened 8 years ago Closed 8 years ago

removeChild(): unexpected title tooltip after removing SVG element at mouse position

Categories

(Core :: General, defect)

x86
All
defect
Not set

Tracking

()

RESOLVED FIXED
mozilla12

People

(Reporter: alice0775, Assigned: longsonr)

References

Details

Attachments

(1 file)

Build Identifier:
http://hg.mozilla.org/mozilla-central/rev/8ae16e346bd0
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0a1) Gecko/20120106 Firefox/12.0a1 ID:20120106031054

this is spun off Bug 693551
Tooltip(title attibute of the element) pops up even if the element has been removed.

Reproducible: Always

Steps to Reproduce:
1. Open Firefox with clean profile

2. Open https://developer.mozilla.org/en/XUL_Tutorial
3. Mouse hover over "Edit" button til tooltip appears,

4. Open attachment 566159 [details]
5. move mouse over circle and click left mouse button (don't stop moving before clicking!)


Actual Results:
  tooltip will pop up.
  
Expected Results:
  Tooltip should not pop up.
Product: Firefox → Core
QA Contact: general → general
Blocks: 639945
OS: Windows 7 → All
Attached patch patchSplinter Review
On the right lines with bug 693551 but compareDocumentPosition actually returns a bitmask: http://mxr.mozilla.org/mozilla-central/source/dom/interfaces/core/nsIDOMNode.idl#119 

In the STR I think DOCUMENT_POSITION_IMPLEMENTATION_SPECIFIC is set too. This is not always the case which is why when I tried it with a slightly different test it worked for me.
Assignee: nobody → longsonr
Attachment #589998 - Flags: review?(dao)
Comment on attachment 589998 [details] [diff] [review]
patch

the explicit Boolean casting shouldn't be needed
Attachment #589998 - Flags: review?(dao) → review+
pushed https://hg.mozilla.org/integration/mozilla-inbound/rev/e70f6f04cf0f without the Boolean casting.
Target Milestone: --- → mozilla12
https://hg.mozilla.org/mozilla-central/rev/e70f6f04cf0f
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.