Closed Bug 271778 Opened 20 years ago Closed 19 years ago

webmessenger locks any current text field

Categories

(Firefox :: General, defect)

x86
Windows Server 2003
defect
Not set
normal

Tracking

()

RESOLVED EXPIRED

People

(Reporter: chris, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

When using the web version of MSN Messenger, incoming messages can freeze typing
into text fields. This isn't just an issue with webmessenger, because it freezes
text input across tabs.

For example, it's happening now. Someone is talking to me in a tab that is for
the webmessenger conversation, and I'm typing in here -- every time they send a
message, I can't type any more. My caret is still positioned in this text field,
but focus seems to have gone elsewhere (pressing backspace in the situation
causes the browser to go back in the page history).

Clicking out of the text field, then back in, will allow typing again.

Sometimes even just within a single tab, the msn messenger text input field will
lock. This is much rarer though.

Reproducible: Always
Steps to Reproduce:
1. Have an MSN account
2. Go to webmessenger.msn.com and sign in
3. Have someone chat to you, whilst you type in the text field on another tab

Actual Results:  
I couldn't type, although the caret was still there as if I should be able to
be. Nothing changed to make the field look 'locked'.

Expected Results:  
Not interfered with my typing ;).
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0
> Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0
> 
> When using the web version of MSN Messenger, incoming messages can freeze typing
> into text fields. This isn't just an issue with webmessenger, because it freezes
> text input across tabs.
> 
> For example, it's happening now. Someone is talking to me in a tab that is for
> the webmessenger conversation, and I'm typing in here -- every time they send a
> message, I can't type any more. My caret is still positioned in this text field,
> but focus seems to have gone elsewhere (pressing backspace in the situation
> causes the browser to go back in the page history).
> 
> Clicking out of the text field, then back in, will allow typing again.
> 
> Sometimes even just within a single tab, the msn messenger text input field will
> lock. This is much rarer though.
> 
> Reproducible: Always
> Steps to Reproduce:
> 1. Have an MSN account
> 2. Go to webmessenger.msn.com and sign in
> 3. Have someone chat to you, whilst you type in the text field on another tab
> 
> Actual Results:  
> I couldn't type, although the caret was still there as if I should be able to
> be. Nothing changed to make the field look 'locked'.
> 
> Expected Results:  
> Not interfered with my typing ;).

This happens to me too with Firefox 1.0, Windows XP Pro.
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.