Bug 16064 - getRangeAt() createRange() error after execCommand('unselect')
Summary: getRangeAt() createRange() error after execCommand('unselect')
Status: CLOSED WORKSFORME
Alias: None
Product: WebKit
Classification: Unclassified
Component: HTML Editing (show other bugs)
Version: 523.x (Safari 3)
Hardware: PC Windows Vista
: P2 Normal
Assignee: Nobody
URL:
Keywords: NeedsReduction
Depends on:
Blocks:
 
Reported: 2007-11-20 03:00 PST by Anders Jenbo
Modified: 2008-03-18 16:08 PDT (History)
2 users (show)

See Also:

Attachments
test case (doesn't fail) (427 bytes, text/html)
2007-12-28 12:38 PST, Alexey Proskuryakov 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
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.