Closed
Bug 500224
Opened 15 years ago
Closed 15 years ago
Crash [@ nsFocusManager::GetCommonAncestor] with onfocus removing window and onload focus
Categories
(Core :: XUL, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: martijn.martijn, Assigned: enndeakin)
References
Details
(Keywords: crash, regression, testcase)
Crash Data
Attachments
(2 files, 1 obsolete file)
486 bytes,
text/html
|
Details | |
2.08 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
See testcase, which crashes current trunk build after a few reloads. The iframe content is this: <html> <body onfocus="window.frameElement.parentNode.removeChild(window.frameElement)" onunload="document.documentElement.focus()"> </body> </html> http://crash-stats.mozilla.com/report/index/7d72d5a5-ab1e-47e8-bb3a-7bc482090624?p=1 0 xul.dll nsFocusManager::GetCommonAncestor dom/base/nsFocusManager.cpp:1129 1 xul.dll nsFocusManager::SetFocusInner dom/base/nsFocusManager.cpp:1050
Assignee | ||
Comment 1•15 years ago
|
||
Need to work out how to get a test for this.
Assignee: nobody → enndeakin
Status: NEW → ASSIGNED
Assignee | ||
Updated•15 years ago
|
Attachment #385155 -
Flags: review?(bzbarsky)
Assignee | ||
Comment 2•15 years ago
|
||
Comment on attachment 385155 [details] [diff] [review] check the in unload state Well I can't figure out how to create a test that fails without the patch and passes with it.
Comment 3•15 years ago
|
||
Comment on attachment 385155 [details] [diff] [review] check the in unload state Don't you need to check both booleans?
Assignee | ||
Comment 4•15 years ago
|
||
Attachment #385155 -
Attachment is obsolete: true
Attachment #386977 -
Flags: review?(bzbarsky)
Attachment #385155 -
Flags: review?(bzbarsky)
Updated•15 years ago
|
Attachment #386977 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 5•15 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/fc3f519cfd44
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Crash Signature: [@ nsFocusManager::GetCommonAncestor]
You need to log in
before you can comment on or make changes to this bug.
Description
•