Closed
Bug 50646
Opened 25 years ago
Closed 25 years ago
changes in XBL files are not reflected
Categories
(Core :: XBL, defect, P3)
Tracking
()
VERIFIED
FIXED
People
(Reporter: wo, Assigned: hyatt)
Details
If you change XBL files while creating a page, those changes are not reflected
in Mozilla until you
a) completely restart Mozilla
b) rename the binding.
I think it would make using bindings much easier if Shift-Reload or a Cache
setting to 0 would prevent this XBL caching.
Steps to reproduce:
Create a HTML page with an XBL binding:
<html>
<head>
<style>
#abutton { behavior:url("abutton.xbl#abutton") }
</style>
</head>
<body>
<button id="abutton">a button</button>
This could be the XBL file "abutton.xbl":
<?xml version="1.0"?>
<bindings xmlns="http://www.mozilla.org/xbl">
<binding id="abutton">
<interface>
<property name="aproperty">17</property>
</interface>
</binding>
</bindings>
Now assume you decide to change aproperty's value from 17 to 18. You modify the
XBL file. What I would expect is that after pressing reload on the HTML page,
the button's aproperty property changes. But it is still 17. To test the updated
binding, I have to rename it (e.g. to bbutton) or close and restart Mozilla.
This happens with M17 Build 2000080712.
|
Assignee | |
Comment 1•25 years ago
|
||
This was fixed in M18.
Status: UNCONFIRMED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
|
|
||
Comment 2•25 years ago
|
||
Works for Me
Platform: PC
OS: Windows 98
Mozilla Version: 2000100508
Marking as Verified
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•