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

Status: RESOLVED INACTIVE

(Core :: XPConnect, defect)

Description

[Jonathan Protzenko [:protz]]

Attachment: 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.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Sounds like a duplicate of the bug on XPConnect swallowing exceptions when there is JS further up the stack.

Comment 2

[Mike Conley (:mconley) (:⚙️)]

I just reproduced this.

Mozilla/5.0 (X11; Linux i686; rv:7.0) Gecko/20100101 Firefox/7.0

Comment 3

[Jonathan Protzenko [:protz]]

The weird thing is, if you do the undefined.foo = "bar" outside of the $() jquery thing, the exceptions shows up in the error console...

Comment 4

[Ben Bucksch (:BenB)]

ban jquery? ;-) *hide*

Comment 5

[:aceman]

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?

Comment 6

[:aceman]

Ah, it is because "modal" was temporarily removed from the dialog in TB :)

Comment 7

[aleth [:aleth]]

This should be gone now.

Comment 8

[aleth [:aleth]]

Oh sorry, for some reason I thought this was a Thunderbird-specific bug, but it's actually in Core.

Comment 9

[BMO Automation]

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.