Severity: normal → major
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: M11
Marking P2/M11. Please let me know if this is more urgent...
I have a similar scenario with the "controller" property of XUL nodes, namely that it needs to be accessible for XUL and HTML, but we're not allowed to modify the HTML. Why don't we put methods off the document, e.g., getController() and getDatabase(), and then we can (for HTML elements only) have a map. I bring this up here because if you do decide to do this, i'd like you to do it for the controller property at the same time.
I was thinking of monkeying around with the script APIs to a property "by hand". I was able to pull this off successfully with the directory viewer stuff...
Not on the critical path. Moving out past M13.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
waterson, could you please verify? I will close this out on Wednesday unless I hear otherwise from you. Thanks!
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: ckritzer → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.