Bug 6574 - Relative offset used to position DHTML tooltip changes with vertical scrolling
Summary: Relative offset used to position DHTML tooltip changes with vertical scrolling
Status: RESOLVED DUPLICATE of bug 8707
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Minor
Assignee: Nobody
URL:
Keywords: NeedsReduction
Depends on:
Blocks:
 
Reported: 2006-01-15 22:20 PST by David Kilzer (:ddkilzer)
Modified: 2006-06-25 18:46 PDT (History)
0 users

See Also:


Attachments
Partially reduced test case (4.45 KB, text/html)
2006-01-15 22:21 PST, David Kilzer (:ddkilzer)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description David Kilzer (:ddkilzer) 2006-01-15 22:20:14 PST
Summary: 

A calculated relative offset used to position a DHTML tooltip changes (becomes larger) as the user 
scrolls vertically down the page.

Steps to Reproduce: 

1. Open test sample (partially reduced from original page) in Safari.
2. Hover mouse pointer over "HoverA" through "HoverE" with veritical scrollbar all the way at the top.  
Note the relative position of the DHTML tooltip.
3. Scroll the vertical scrollbar all the way down to the bottom.
4. Hover mouse pointer over "HoverA" through "HoverE" again.  Note position of DHTML tooltip, and 
compare to Firefox 1.5.

Expected Results: 

The DHTML tooltip window should always stay close to the element being hovered over.  (Compare with 
behavior in Firefox 1.5, for example.)

Actual Results: 

The DHTML tooltip is rendered farther and farther down the page (vertically) the more the user scrolls 
the page down vertically.

Regression: 

Same behavior occurs in Safari 2.0.3 (417.8) in Mac OS X 10.4.4.

Notes: 

None.
Comment 1 David Kilzer (:ddkilzer) 2006-01-15 22:21:39 PST
Created attachment 5712 [details]
Partially reduced test case

Attaching a partially reduced test case from the original web site.
Comment 2 David Kilzer (:ddkilzer) 2006-06-24 20:42:40 PDT
This may be a duplicate of Bug 8707.  The JavaScript in the test case (Attachment 5712 [details]) may be setting the ie/ns6 variables wrong and/or making the wrong assumptions, too.
Comment 3 David Kilzer (:ddkilzer) 2006-06-25 18:46:49 PDT
This was fixed by the patch for Bug 8707.  W00t!



*** This bug has been marked as a duplicate of 8707 ***