248265 - Simulated mouse input

Status: RESOLVED INCOMPLETE

(Core :: Widget, defect)

Description

[Jason]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705; .NET CLR 1.1.4322)
Build Identifier: 1.6

I am working on a desktop replacement app and Mozilla does not respond to any 
simulated mouse input... it is the only program I have come across that 
doesn't and I have looked at the code and am still not sure why. Basically I 
have a representantion of the browser that a user clicks on and I figure out 
mouse messages to send.. I have duplicated the messages sent via normal usage. 





Reproducible: Always
Steps to Reproduce:
1.Send a WM_MOUSEUP/WM_MOUSEDOWN event to a location in the client area where 
a link is located
2.possibly send WM_PARENTNOTIFY messages to parents
3.possibly send same messages to window with captured focus

Actual Results:  
absolutely nothing happens

Expected Results:  
mozilla should react as if the mouse was moved over the link ( assuming it 
gets the WM_MOUSEMOVE messages up to that point ) and the left mouse button 
was clicked, by loading up the page the link refers to.

I can supply a sample application I am using for testing purposes so you can 
see that I am sending all the correct messages in the right order and at the 
right time.

Also, I am not and cannot use journal hooks since the mozilla window is not 
actually on screen.

Comment 1

[Gervase Markham [:gerv]]

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 2

[Ere Maijala (slow)]

Doug, this might be the one you'll want to work on.

Comment 3

[Wayne Mery (:wsmwk)]

Ere, is this a confirmed problem?
(I suspect reporter is gone)

Comment 4

[Wayne Mery (:wsmwk)]

Doug, any reason to believe this does, or ever did, exist?

Comment 5

[Matthias Versen [:Matti]]

marking incomplete, please reopen if this is still an issue