W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2011

[Bug 15356] New: NodeFilter callback

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Dec 2011 15:47:37 +0000
To: www-dom@w3.org
Message-ID: <bug-15356-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15356

           Summary: NodeFilter callback
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM
        AssignedTo: annevk@opera.com
        ReportedBy: annevk@opera.com
         QAContact: member-webapi-cvs@w3.org
                CC: ian@hixie.ch, mjs@apple.com, ap@webkit.org,
                    mike@w3.org, simonp@opera.com, Olli.Pettay@gmail.com,
                    jonas@sicking.cc, Ms2ger@gmail.com, ayg@aryeh.name,
                    travil@microsoft.com, jrossi@microsoft.com,
                    www-dom@w3.org, ojan@chromium.org


I would like your help in figuring out how we should define NodeFilter per the
latest Web IDL as implementations might have to change.

http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#nodefilter
http://dev.w3.org/2006/webapi/WebIDL/

The simplest I could come up with was to put all the constants on an exposed
NodeFilter interface and put the acceptNode() method on a separate
NodeFilterCallback callback interface.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Wednesday, 28 December 2011 15:47:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:09 GMT