Closed
Bug 500968
Opened 16 years ago
Closed 16 years ago
XBL is not triggered inside overlay
Categories
(Core :: XBL, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: atg2dg, Unassigned)
References
Details
(Keywords: regression, testcase)
Attachments
(1 file)
2.22 KB,
application/x-xpinstall
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1) Gecko/20090624 Firefox/3.5 (.NET CLR 3.5.30729)
I have an extension which uses XBL element inside an overlayed toolbar. Inside the overlay there is a label 'test' which should have displayed (at least it displays in Firefox 3.0.11). The element containing the XBL is there when i inspect with DOM Inspector but the XBL content is missing.
Reproducible: Always
Steps to Reproduce:
1. Install the example extension i attach
Actual Results:
Nothing displays in the toolbar
Expected Results:
It should display a label with text 'test'
Comment 2•16 years ago
|
||
Confirmed on Windows Vista. I don't see errors.
Regression range is http://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=5c289d7b5f17&tochange=55f801c97764
which seems to be bug 425153.
Can't look into this bug nor make it blocking.
Status: UNCONFIRMED → NEW
Component: Extension Compatibility → DOM
Ever confirmed: true
Keywords: regression,
testcase
Product: Firefox → Core
QA Contact: extension.compatibility → general
Version: unspecified → 1.9.1 Branch
Updated•16 years ago
|
Component: DOM → XBL
QA Contact: general → xbl
![]() |
||
Comment 3•16 years ago
|
||
The extension is using xpcnativewrappers=no (why? I have no idea; that's not exactly a safe thing to do). The fix for bug 425153 makes it so that a document that uses xpcnativewrappers (e.g. the browser window) cannot have a binding that wouldn't use xpcnativewrappers applied to its nodes. So the behavior is as expected.
You probably want to take out the "xpcnativewrappers=no" line in your manifest...
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → INVALID
Comment 5•16 years ago
|
||
The Firefox 3.5 "updating extensions" article has a blurb on this now. Couldn't find anywhere else that really stood out as needing to mention it, so if you find a place for it, please do say something about it.
You need to log in
before you can comment on or make changes to this bug.
Description
•