expose implementation of nsIDOMNodeList

RESOLVED WONTFIX

Status

()

Core
DOM
RESOLVED WONTFIX
11 years ago
5 months ago

People

(Reporter: surkov, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

11 years ago
It's needed to have implementation of nsIDOMNodeList available for other modules than content. Content has implemnetation of nsIDOMNodeList like nsBaseContentList (nsContentList.h). Usecase of nsIDOMNodeList creation is in xforms extension (http://lxr.mozilla.org/mozilla/source/extensions/xforms/nsXFormsUtilityService.h#110).
(Reporter)

Comment 1

11 years ago
Olli, I guess you are right and it would be great if new interface will be exposed (though I'm not sure whether this interface should be scriptable or not). I covered once that it's fine to have indexOf method on nsIDOMNodeList. Therefore probably methods like appendItem/removeItem would be fine there too. Who can approve an idea to introduce new interface for nsIDOMNodeList objects?
Assignee: general → nobody
QA Contact: ian → general
(In reply to comment #1)

surkov: Perhaps you should resummarize to indicate your intent?  If you're talking about having a nsIDOMNSNodeList interface with, say, .concatenate(in nsIDOMNodeList list), maybe the bug summary should reflect that.
(Reporter)

Comment 3

8 years ago
Alex, I'm not sure, it could be
1) c++ class, I can create an instance of it outside content module
2) xpcom component exposing new interface to modify list items
3) something in the middle
Chrome JS has ChromeNodeList.

C++ consumers can just create subclasses as needed, since it's all in libxul now.
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.