Open
Bug 435001
Opened 16 years ago
Updated 2 years ago
persist data not working in bindings
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
UNCONFIRMED
People
(Reporter: open, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; sk-SK; rv:1.8.1.14) Gecko/20080404 Firefox/2.0.0.14 Build Identifier: Firefox 2.0.0.14 when persist attribute is in .xbl defined and this .xbl is by class used in xul document, persist is not applied. classical .xul document works. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Comment 1•16 years ago
|
||
Persistence is done by id. Since IDs in XBL are non-unique pretty much by definition, and since the XBL anonymous content is not accessible from the DOM, I certainly wouldn't expect this to work. But in any case, it sounds like a XUL issue, not an XBL one.
Component: XBL → XP Toolkit/Widgets: XUL
QA Contact: xbl → xptoolkit.xul
Reporter | ||
Comment 2•16 years ago
|
||
yes I know how persist data works with uri and unique id. but how can be solved problem of persistent data in XUL defined by XBL? (for example i'm using on several places listing of articles/users/images of our open-source CMS which is defined by .xbl, and users can't setup using this standardized way which columns are enabled/disabled) btw: sorry for my english
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: xptoolkit.xul → xptoolkit.widgets
Comment 3•12 years ago
|
||
Since this will probably never be fixed, a simple workaround is to put attributes on the xbl instanciated node, and to use xbl:inherits and DOM Mutation Observers to keep attributes synchronized. This can be very heavy, having a LOT of attributes in your instance.
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•