Closed
Bug 635086
Opened 14 years ago
Closed 14 years ago
Creating modal windows raise an exception
Categories
(Toolkit :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: kidkog, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:2.0b11) Gecko/20100101 Firefox/4.0b11
Build Identifier: Mozilla/5.0 (X11; Linux i686; rv:2.0b11) Gecko/20100101 Firefox/4.0b11
In Firefox 4.0 Beta 11, attempting to create a modal window raises an "uncaught exception" in the Error Console, which stops Javascript execution.
Reproducible: Always
Steps to Reproduce:
1. Type "javascript:alert('test')" into the address bar
Actual Results:
Nothing happens on-screen, and in the error console, the following message appears:
Error: uncaught exception: [Exception... "'[JavaScript Error: "winUtils.enterModalState is not a function" {file: "resource://gre/components/nsPrompter.js" line: 424}]' when calling method: [nsIPrompt::alert]" nsresult: "0x80570021 (NS_ERROR_XPC_JAVASCRIPT_ERROR_WITH_DETAILS)" location: "JS frame :: javascript:alert('test') :: <TOP_LEVEL> :: line 1" data: yes]
Expected Results:
An alert with the text "test" should show up.
This is the first beta that this bug occurs in. b10 and before did not have this issue.
Comment 1•14 years ago
|
||
tested on both mac and linux nightlies, 2011-02-17. Works here.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
I just downloaded 4.0 RC 1, and the test case above still fails on my end.
Not sure if it's my environment or not... XFCE 4.6.1. Note that real alerts that have their own window, such as alert()s from the Error Console, work just fine.
Just to make sure nothing weird was going on, I downgraded to 4.0b10 again, and the alert worked just fine. Re-upgrading to RC1 re-introduced the error.
I also upgraded to XFCE 4.8.0, thinking that maybe 4.6 was just outdated, but to no avail. Error is still present.
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Comment 4•14 years ago
|
||
ccing dolske to see if he can make sense of this. Still works here on OS X. Your window manager shouldn't have anything to do with alert dialogs as they're rendered by Firefox now.
Component: Developer Tools → General
QA Contact: developer.tools → general
Comment 5•14 years ago
|
||
You still get the _exact_ same error message? Because it was replaced with a call to winUtils.enterModalStateWithWindow(). [Note longer function name.]
Can you reproduce this with a clean new profile?
Product: Firefox → Toolkit
QA Contact: general → general
On my default profile, yes, I still get the error message.
However, I created a test (blank) profile and my test case worked just fine, no error in sight.
Thanks for everybody's help on fixing this ebkac error.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago → 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•