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

https://www.w3.org/Bugs/Public/show_bug.cgi?id=14591

--- Comment #7 from Aryeh Gregor <ayg@aryeh.name> 2012-05-03 11:31:24 UTC ---
Gecko is experimenting with making Range.detach() a no-op for Firefox 15. 
Currently it's in nightlies, and I don't think we've received any complaints of
broken pages yet, but it's only been a few days.  If it gets to stable and we
still have no or almost no problem reports, I think it's definitely worth
speccing it as a no-op.

Removing it entirely is probably a bad idea.  I've seen code (including in
Gecko's own non-detach()-related test support code) that pointlessly calls
detach() after it's done with the range and doesn't intend to use it again. 
Probably this is based on the theory that any associated storage can be freed
at that point or something -- although Gecko never actually did that AFAICT.

Ms2ger, Anne, are you okay with us updating the spec now to have an XXX about
this?  I'd wait a little longer before changing the spec to match Gecko, in
case problems arise.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 3 May 2012 11:31:32 UTC