Closed
Bug 372380
Opened 17 years ago
Closed 7 years ago
expose implementation of nsIDOMNodeList
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: surkov, Unassigned)
Details
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•17 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?
Updated•15 years ago
|
Assignee: general → nobody
QA Contact: ian → general
Comment 2•14 years ago
|
||
(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•14 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
Comment 4•7 years ago
|
||
Chrome JS has ChromeNodeList. C++ consumers can just create subclasses as needed, since it's all in libxul now.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•