If in an IFrame, clientY will return wrong value if another iframe is displayed and hidden




Event Handling
14 years ago
12 years ago


(Reporter: Mike Sywensky, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)



(1 attachment)



14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030728 Mozilla Firebird/0.6.1

'Base page' has an IFrame that is visible.  ClientX and ClientY are correct for
events in the IFrame.  The base page then displays another IFrame over the
original IFrame and then hides it.  The events in the original IFrame now have a
ClientY value calculated based upon the top window, and not the IFrame.  The
ClientX values still appear to be correct.

Sample code will be attached.

Reproducible: Always

Steps to Reproduce:
1.Check ClientY.
2.Open and close new IFrame
3.Check ClientY.

Actual Results:  
Step one produces a ClientY based upon the IFrame.  Step 3 produces a ClientY
based upon the top window.

Expected Results:  
Steps one and three should produce the same result.

Comment 1

14 years ago
Created attachment 133273 [details]
test pages... open testIFrame.html in a browser

Comment 2

14 years ago
Yes, this is true. Plus there is a problem with vertical scrolling. The vertical
scrollbar handle cannot be grabbed, it behaves as if the handle is positioned
lower than it is displayed. If you grab the "empty space" below the handle, is
scrolls all right. I think the mouse is not captured where the handle is (Y
coordinate, X coordinate is fine).

Comment 3

13 years ago
This bug still exists.  Displaying two IFrames, and hiding the top IFrame causes
the clientx and y values to be skewed.  Any drawing that depends upon the
values, such as the context menu, appear in the wrong place.

Comment 4

13 years ago
related to bug 108591 (just guessing) ?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 6

12 years ago
The bug does not appear in 1.5B1.  It appears to be fixed.
Last Resolved: 12 years ago
Resolution: --- → FIXED

Comment 7

12 years ago
No specific bug / patch referred to as the fix.


(Perhaps the automated bug closure should resolve as WORKSFORME rather than
Resolution: FIXED → ---


12 years ago
Last Resolved: 12 years ago12 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.