469178 - XBL binding no longer works if the xpcnativewrappers security mechanism is disabled for an extension

Status: UNCONFIRMED

(Core :: DOM: Core & HTML, defect, P5)

Description

[Michael Kraft [:morac]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2

I have an extension where binding stopped working after upgrading to Firefox 3.1b2.  I couldn't figure out why since the elements in question were correctly pointing to the xml file in the "-moz-binding" CSS, and changing the -moz-binding" CSS to an XML file not included in the extension worked fine.

I finally tracked down the problem to the following line in my chrome.manifest file:

content	extension jar:chrome/extension.jar!/content/extension/ xpcnativewrappers=no

When I removed the "xpcnativewrappers=no" text, everything worked fine.  So binding doesn't work if "xpcnativewrappers=no"


Reproducible: Always

Steps to Reproduce:
1.  Add "xpcnativewrappers=no" to a content line in chrome.manifest for an extension that uses XBL binding
2.
3.
Actual Results:  
Binding does not occur.  DOM Inspector shows that there is no XBL bindings for the element even thought the -moz-binding CSS property is set correctly.

Expected Results:  
Binding should work like it did in Firefox 3.0 and 3.1b1.

The only thing I could find that might cause this is bug 424733, but the fact that I  don't see the problem in Firefox 2.0.0.18 or Firefox 3.0.4 (both which are supposed to have the fix for bug 424733 in it) seems to indicate that's not the cause.

Comment 1

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1472046

Move all DOM bugs that haven’t been updated in more than 3 years and has no one currently assigned to P5.

If you have questions, please contact :mdaly.