Bug 16064

Summary: getRangeAt() createRange() error after execCommand('unselect')
Product: WebKit Reporter: Anders Jenbo <fuck>
Component: HTML EditingAssignee: Nobody <webkit-unassigned>
Status: CLOSED WORKSFORME    
Severity: Normal CC: ap, webkit
Priority: P2 Keywords: NeedsReduction
Version: 523.x (Safari 3)   
Hardware: PC   
OS: Windows Vista   
Attachments:
Description Flags
test case (doesn't fail) none

Description Anders Jenbo 2007-11-20 03:00:52 PST
After calling execCommand('unselect' false, NULL) on a desigMode iframe, all subsequent call to getRangeAt() or createRange() will result in a script faliuer. in this case rangeCount is eual to 0, after a failed createRange(), getRangeAt() or alert() every thing will be working again.
Comment 1 Anders Jenbo 2007-11-20 03:01:28 PST
Making a selection will also solve the issue.
Comment 2 Mark Rowe (bdash) 2007-11-20 12:51:28 PST
A test case would be very helpful to demonstrate the issue here.
Comment 3 Alexey Proskuryakov 2007-12-28 12:38:03 PST
Created attachment 18151 [details]
test case (doesn't fail)

I have tried to make a test case, but couldn't get it to fail. We won't be able to do much with this bug without more information.
Comment 4 Robert Blaut 2008-03-18 14:37:06 PDT
(In reply to comment #3)
> Created an attachment (id=18151) [edit]
> test case (doesn't fail)
> 
> I have tried to make a test case, but couldn't get it to fail. We won't be able
> to do much with this bug without more information.
> 

Anders, after many months without providing more details regarding this issue I have to close the report. Feel free to reopen it if you provide more details.
Comment 5 Anders Jenbo 2008-03-18 16:08:29 PDT
I currently have a work around in place and won't have time to deal with it for a long time so closing it is fine.