92252 - Crash in DOM timer code when visiting quios.com

Status: RESOLVED WORKSFORME

(Core :: DOM: UI Events & Focus Handling, defect, P1)

Description

[Matthias Versen [:Matti]]

win23k build 20010725..
I tried to reproduce bug 92239 and I saw this.

I hope this component is correct. Or is this DOM 0 or HTML Form Controls ?

1. open that URL
2. Type in the message field.
- Now bring another window in the foreground. This page steals the focus all x   
  secounds.
- Try to mark a part of that URL in the URL box - impossible
- try to type in the last form "Email adress"

Comment 1

[Matthias Versen [:Matti]]

Warning:
You can easy crash here. (bug 55459)

Comment 2

[saari (gone)]

looks like that message field is infinite looping a focus switch between the
message and message length fields.

0.9.4 P1

Comment 3

[saari (gone)]

Okay, I think I have a patch to fix the window jumping to front issue, but it 
doesn't fix the inability to type in the other forms. Now, if I change the 
page's JS to use the IE targeted code, it works fine. If you read the JS code 
and play with it, we are doing what I believe is the correct thing, stealing 
focus back to the message field, just as specified. Why this works in 4.x I 
don't know.

Comment 4

[saari (gone)]

Attachment: the patch I spoke of above

Comment 5

[saari (gone)]

uh oh, test case went away

Comment 6

[Peter Trudelle]

nsbeta1- per ADT triage team

Comment 7

[Matthias Versen [:Matti]]

saari : can we close this one (no testcase..) ?

Comment 8

[Brant Gurganus]

By the definitions on <http://bugzilla.mozilla.org/bug_status.html#severity> and
<http://bugzilla.mozilla.org/enter_bug.cgi?format=guided>, crashing and dataloss
bugs are of critical or possibly higher severity.  Only changing open bugs to
minimize unnecessary spam.  Keywords to trigger this would be crash, topcrash,
topcrash+, zt4newcrash, dataloss.

Comment 9

[Matthias Versen [:Matti]]

-> wfm