W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

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

From: <bugzilla@jessica.w3.org>
Date: Wed, 28 Nov 2012 17:11:11 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-14591-2532-lp9UDmayxT@http.www.w3.org/Bugs/Public/>

Tim Down <timdown@gmail.com> changed:

           What    |Removed                     |Added
                 CC|                            |timdown@gmail.com

--- Comment #13 from Tim Down <timdown@gmail.com> ---
I'm in favour of getting rid of detach() because its existence is confusing,
but I still have some residual confusion. I had assumed that the reason for
detach()'s existence was because a range needs to observe the DOM in order to
update itself when the DOM changes, which must have some performance
implication. Was I mistaken? If not, is the process of detaching a range now
handled when the range is garbage collected?

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 28 November 2012 17:11:19 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:04:28 UTC