Closed Bug 12441 Opened 20 years ago Closed 20 years ago

'database' attribute does not get created on HTML template "datasources node"

Categories

(Core :: XUL, defect, P2, major)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: waterson, Assigned: waterson)

Details

If you have a template whose "datasources node" is an HTML element, the
"database" attribute is inaccessable from JavaScript; e.g.,

<select datasources="rdf:bookmarks" ref="NC:BookmarksRoot" id="foo">
  <template>
    <option uri="...">

---

var s = document.getElementById('foo');
s.database.Unassert(...); // database undefined!

This has to do with the funky way I've hooked up the generic builder in the
HTML case.
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...
Target Milestone: M11 → M15
Not on the critical path. Moving out past M13.
Status: ASSIGNED → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
waterson, could you please verify?  I will close this out on Wednesday unless I
hear otherwise from you.  Thanks!
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: ckritzer → xptoolkit.widgets
You need to log in before you can comment on or make changes to this bug.