Closed Bug 688273 Opened 10 years ago Closed 3 years ago

All exceptions silently swallowed when opening a page (that loads jquery) with the modal parameter

Categories

(Core :: XPConnect, defect)

x86_64
Linux
defect
Not set
normal

Tracking

()

RESOLVED INACTIVE
Tracking Status
platform-rel --- -

People

(Reporter: protz, Unassigned)

Details

(Whiteboard: DUPEME)

Attachments

(1 file)

Attached file Small testfile
This is the strangest bug. Here's a testfile that you can save in /tmp. Then, in the Error Console, run:

openDialog("file:///tmp/mini.html", "", "chrome,width=100,height=100,modal")

--> no exception in the error console

openDialog("file:///tmp/mini.html", "", "chrome,width=100,height=100")

--> exception in the error console

Tested on a recent Gecko.
Sounds like a duplicate of the bug on XPConnect swallowing exceptions when there is JS further up the stack.
Component: DOM → XPConnect
QA Contact: general → xpconnect
Whiteboard: DUPEME
I just reproduced this.

Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20100101 Firefox/7.0
The weird thing is, if you do the undefined.foo = "bar" outside of the $() jquery thing, the exceptions shows up in the error console...
ban jquery? ;-) *hide*
For some reason I see the ton of jquery warnings in the error console (when opening the account provisioner). Is it only when strict warnings are enabled?
Ah, it is because "modal" was temporarily removed from the dialog in TB :)
Depends on: 1014609
This should be gone now.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
Oh sorry, for some reason I thought this was a Thunderbird-specific bug, but it's actually in Core.
Status: RESOLVED → REOPENED
No longer depends on: 1014609
Resolution: WORKSFORME → ---
Whiteboard: DUPEME → DUPEME [platform-rel-jQuery]
platform-rel: --- → ?
platform-rel: ? → -
Whiteboard: DUPEME [platform-rel-jQuery] → DUPEME
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: REOPENED → RESOLVED
Closed: 6 years ago3 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.