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

VERIFIED FIXED in M15

Status

()

Core
XUL
P2
major
VERIFIED FIXED
19 years ago
a year ago

People

(Reporter: Chris Waterson, Assigned: Chris Waterson)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

19 years ago
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.
(Assignee)

Updated

19 years ago
Severity: normal → major
Status: NEW → ASSIGNED
Priority: P3 → P2
Target Milestone: M11
(Assignee)

Comment 1

19 years ago
Marking P2/M11. Please let me know if this is more urgent...

Comment 2

19 years ago
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.
(Assignee)

Comment 3

19 years ago
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...
(Assignee)

Updated

19 years ago
Target Milestone: M11 → M15
(Assignee)

Comment 4

19 years ago
Not on the critical path. Moving out past M13.
(Assignee)

Updated

19 years ago
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED

Comment 5

19 years ago
waterson, could you please verify?  I will close this out on Wednesday unless I
hear otherwise from you.  Thanks!
(Assignee)

Updated

19 years ago
Status: RESOLVED → VERIFIED

Comment 6

18 years ago
BULK MOVE: Changing component from XUL to XP Toolkit/Widgets: XUL.  XUL 
component will be deleted.
Component: XUL → XP Toolkit/Widgets: XUL

Updated

10 years ago
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.