Security Manager vetoed action arg 0 NS_ERROR_XPC_SECURITY_MANAGER_VETO

[laxdragon]

This is a new error with Firefox 11. I'm not sure if this is an error in the core of jquery, or if it is with html5 upload. Anyone else getting this? The same upload code still works in FF 10 and in Chrome.

Full error from FF Console:

Error: uncaught exception: [Exception... "Security Manager vetoed action arg 0 [nsIDOMHTMLDivElement.contains]" nsresult: "0x80570027 (NS_ERROR_XPC_SECURITY_MANAGER_VETO)" location: "JS frame :: :: <TOP_LEVEL> :: line 3" data: no]

[laxdragon]

After some further research, I discovered the bug is actually somewhere in jquery-ui. I use that to display my progress dialog, such as:

        onStart: function(event, total)
        {
            var msg = $("#progress_report_template").clone();
            $("#dialog").html($(msg).html());
            $("#dialog").dialog(
            {
                title: $(msg).find('.dialog_title').text(),
                resizable: false,
                height: 'auto',
                width: 400,
                modal: true,
                show: "slide",
                hide: "slide",
                buttons: { Close: function (){ $("#dialog").dialog("close"); }}
            });
            return true;
        },

With jquery-ui 1.8.18, it would raise an exception in Firefox (any version, not just 11). Reverting to a previous version fixes this issue. So no bug in html5-upload itself. Closing...

[coling]

Just for reference, I found this bug report while debugging the same issue in our own custom jquery stuff (also an upload wrapper funnily enough but that's unrelated to the problem)

With the hint provided by this ticket I found the regression for me came between versions 1.8.15 -> 1.8.16 of jQuery UI. Further bisecting and I found the first problem commit upstream to be:
jquery/jquery-ui@82df692

Indeed reverting this commit in later jQuery UI versions solved the problem for me.

If you still have a test case around, it would be nice if you could confirm this.

For reference, the ticket related to this commit (i.e. the problem it was trying to solve) is:
http://bugs.jqueryui.com/ticket/7595

Hope this helps.

Col

[laxdragon]

I can now confirm that jquery-ui 1.8.21 does fix the issue I encountered.
http://bugs.jqueryui.com/ticket/8288