274093 - Wrong Cursor placement in entry fields if RealPush is running in another TAB or Window

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[udo]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; DT; .NET CLR 1.1.4322)
Build Identifier: 

The cursor within an entry field (text and numerics) is wrongly placed during 
the entry procedures if in a second window or TAB RealPush data is displayed. 
This causes wrong data to be entered and transmitted. This problem exist on 
Mozilla 1.1 / 1.3 / 1.8a5 and Firefox V 1.0. It does NOT exist on the MS 
Internet Explorer 6.0. The problem exist on the java engine j2re1.4.2_05 + _06 
and the operating system W2000 + XP. 

Reproducible: Always
Steps to Reproduce:
1.Open a tab and display RealPush data via Internet with permanent updates 
(e.g. stock quotes from onvista.de - requires a no cost login).
2.Open a 2nd tab to any link requesting data input
3.Input data in any entry field and watch the sequence of the input data

Actual Results:  
Key entries will be out of the typed sequence in the entry field because the 
entry cursor is misplaced. E.g. if one types 1234, the entry field will contain 
the correct digits but in the wrong sequence - result might look 1243. 

Expected Results:  
This is a very nasty and dangerous error. If you have any transactions running 
like selling or buying shares, money transfer etc. this error might cause 
serious harm to your bank account. Imagine transferring $100.00 and putting the 
number 100.00 in the entry field it might come out to 10000. and this will be 
accepted as $10,000.00 money transfer. Wish my boss would use this browser.

The problem seems to be related to the display of RealPush data in a 2nd 
Mozilla window. If the RealPush window is closed the above mentioned error does 
not occur. If the RealPush data is diplayed in a MS Internet Explorer window in 
parallel, no malfunction occurs. The error exist - as described above - on W2k 
and XP. Please pay attention to the fact that the error occurs when the 
RealPush window gets updated. If you need a login for the above mentioned stock 
quotes link (www.onvista.de) send me a mail - I would request a login for you. 
For testing keep the time zone in mind to get quote updates.

Comment 1

[Andrew Schultz]

I found this:
http://lsd.realpush.onvista.de/livehtml/stocks.html?ID=LS_DAX&ID_ISSUER_GROUP=53156
and clicked on one of the graphics in the right column.  It brought up a window
with a Java plugin.  Is that the real push?  Of course, it's the weekend, so
nothing exciting.  Does it need to be actively updating to hit the bug?

Several focus-stealing bugs have been fixed recently.  You might try with a
recent trunk build to see if this problem has already been fixed.

Comment 2

[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 3

[Gervase Markham [:gerv]]

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.