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

[Bug 14591] New: Get rid of Range.detach()

From: <bugzilla@jessica.w3.org>
Date: Fri, 28 Oct 2011 19:35:40 +0000
To: www-dom@w3.org
Message-ID: <bug-14591-4009@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14591

           Summary: Get rid of Range.detach()
           Product: WebAppsWG
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: P2
         Component: DOM Core
        AssignedTo: annevk@opera.com
        ReportedBy: ayg@aryeh.name
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, www-dom@w3.org


It's absolutely useless, and it adds a line to every single Range attribute and
method definition.  Skimming Code Search turns up no usage of Range.detach() in
the first few pages (jquery/mootools omitted because they define methods by
that name that occur a lot):

http://www.google.com/codesearch#search/&q=lang:%5Ejavascript$%20function:%5Edetach$%20-file:(%5E%7C/)jquery.*%5C.js$%20-file:mootools%5C.js$&type=cs

Are implementers willing to drop support here?  Are there sites that actually
use it?  I find four crash bugs in Gecko when searching for "range detach", so
clearly enough people must be using it for those to get reported.  If that's
too big a compat risk, can we make it a no-op?

-- 
Configure bugmail: http://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 Friday, 28 October 2011 19:35:50 GMT

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