text element key event coordinates are not set




16 years ago
13 years ago


(Reporter: rsh, Assigned: joki)



Firefox Tracking Flags

(Not tracked)





16 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:1.2a) Gecko/20020910

Key events targeted at text elements don't get their Javascript coordinate
properties (x, y,pageX, pageY, screenX, screenY) set.  Values reported are
undefined or 0.

Reproducible: Always

Steps to Reproduce:
1. Load test page.  It tests only for the KEYPRESS event handled at window, but
can be modified to test for KEYUP, KEYDOWN, and for activation at target. 
2. Type keys at the textbox and textarea. 
3. Each KEYPRESS event is caught by a window-level onkeypress handler which
displays in the window status area a handler activation counter, eventObj.which,
eventObj.x , eventObj.y and eventObj.pageX, eventObj.pageY.

Actual Results:  
KEYDOWN:  MOZ: handler not activated    NN4.79: correct coords
KEYPRESS: MOZ: coords not set           NN4.79: correct coords
KEYUP:    MOZ: coords not set           NN4.79: correct coords

MOZ reports x = y = undefined; pageX = pageY = (also screenX = screenY) = 0.
Same results if handler is activated at target instead of window using

This breaks existent pages and significantly restricts key-driven DHTML
interface design.

Expected Results:  
All coords should be set correctly for all key events, regardless of level where
handler is activated.
Note that in the DOM spec screen coordinates are something specific to mouse

Comment 2

16 years ago
Broken keydown on Mac is bug 148130.

Comment 3

16 years ago
I'm seeing the same behavior on WinXP, moz 1.2a.  Setting All/All
OS: Mac System 9.x → All
Hardware: Macintosh → All


16 years ago
QA Contact: rakeshmishra → trix

Comment 4

16 years ago
Robert - can you give an example of an existing page which this breaks? I just
tried in IE (6 on Windows), and your testcase doesn't work there.  If IE doesn't
implement this and it's not in the standard, then I'm not sure that anyone is
going to be convinced to implement it.

Comment 5

16 years ago
reporter replied to me by email: (Bob - for future reference, it's better if you
go to the bugzilla web form - the URL is in the bugzilla emails - and post the
comments through that, rather than emailing them...)

On Mon, Jan 06, 2003 at 04:46:22PM -0600, Robert Hart wrote:
> Thanks for you attention to this.  Sorry to delay reply, but was out
> of office during the holidays.
> It breaks
>      http://www.lll.uiuc.edu/hum382/judgeResponse/judgeResponse.html
> This page is a fill-in-the blanks ESL exercise which gives error
> feedback in the left margin, vertically positioned to align it with
> the current text element.  It is implemented by a "driver" program
> which reads the visible exercise content as data (in the form of an
> HTML page) and presents it with program-generated blanks.  The driver
> uses the position attributes of the text elements to assure that the
> feedback is positioned at the correct vertical location.  Since it is
> a template program, I, my students, and various others have produced
> a number of data pages that implement various exercises, & I expect
> more to be implemented as time goes on.  They work fine in NN4.7, but
> stopped working with Moz.  They don't work in IE because none of my
> development work supports IE (unless by accident).
> Clearly the real issue is not the availability of these attributes,
> but some general mechanism to determine the current screen position
> of any HTML element, including those AUTO positioned; the (apparent)
> lack of this capability is a constant difficulty when trying to build
> interfaces like this.
> Bob Hart

Comment 6

14 years ago
I observe that text coordinates for the text are wrong (x=0,y=0,w=0,h=0) for the
text from the "Location" text-box (Edit->Preferences).
This is the cause of gnopernicus bug:
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/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.