Closed Bug 390664 Opened 14 years ago Closed 12 years ago

observes tag in xbl has context not in xul


(Firefox :: General, defect)

2.0 Branch
Not set





(Reporter: richard, Unassigned)


(Whiteboard: [CLOSEME 5-15-2010])


(3 files)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20061201 Firefox/ (Ubuntu-feisty)
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20061201 Firefox/ (Ubuntu-feisty)

using an observes tag in xbl definition of a new widget to monitor curpos attribute in scrollbox. If the observes tag is ABOVE the scrollbox, an onbroadcast event is triggered. If BELOW, onbroadcast is NOT triggered. Strange!!!

Simulating the same XUL directly in an XUL file, with not XBL, did not cause the error.

problem.xul problem.css and problem.xml attached to demonstrate XBL behavior. 

Reproducible: Always

Steps to Reproduce:
1.load problem.xul file attached to this report
2.move the upper scrollbar
3.move the lower scrollbar
Actual Results:  
1. When upper scrollbar is moved, and alert is shown
2. When lower scrollbar is moved, no alert is shown

Expected Results:  
an alert should have been triggered in both cases
Attached file css file for widgets
slight error in "expected results" of original report: Upper scrollbar does NOT trigger alert. Lower scrollbar DOES trigger alert.

Other that the placing of the scrollbar and the scrollbox within the xbl definition, and naming them slightly differently, there is absolutely no difference between the code.
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
Whiteboard: [CLOSEME 5-15-2010]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Closed: 12 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.