The current implementation of nsXULDataSource is not (?) being used. We _do_ need a XUL datasource, but the _only_ thing it needs to do is wrap the in-memory datasource, and then forbid updates once the document is done loading. This way, were sure not to get any accidental sharing.
Status: NEW → ASSIGNED
QA Contact: 4015 → 3524
Target Milestone: M6
Status: ASSIGNED → RESOLVED
Last Resolved: 20 years ago
Resolution: --- → INVALID
Never mind. This is stupid.
Status: RESOLVED → VERIFIED
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL. XUL component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: waterson → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.