Bug 8497

Summary: Editable Area loses selection when losing focus
Product: WebKit Reporter: webkit
Component: HTML EditingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: ddkilzer, ian, mrowe
Priority: P2    
Version: 417.x   
Hardware: Mac   
OS: OS X 10.4   
URL: http://www.fredck.com/bugs/safari/iframefocus/iframefocus.html
Bug Depends on:    
Bug Blocks: 9915    
Attachments:
Description Flags
Test Case none

webkit
Reported 2006-04-20 04:13:30 PDT
When defining an IFRAME with an editable document, clicking outside the IFRAME and then calling IFRAME.focus(), the caret is placed in the beginning of the editable area and the previous selection is lost. The URL shows a simple test case for it.
Attachments
Test Case (1.23 KB, application/octet-stream)
2006-04-20 04:14 PDT, webkit 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
webkit
Comment 1 2006-04-20 04:14:48 PDT
Created attachment 7848 [details] Test Case
Mark Rowe (bdash)
Comment 2 2006-07-02 07:13:41 PDT
Confirmed in WebKit 418.8 and the latest nightly. The behaviour differs slightly in the nightly in that the selection is correctly rendered as inactive when it loses focus, but upon restoration of focus the selection is still lost.
David Kilzer (:ddkilzer)
Comment 3 2006-07-17 15:14:57 PDT
This bug sounds very similar to Bug 9642. Please check a nightly WebKit build on or after r15487 (Bug 9642 Comment #7) to see if this is fixed.
David Kilzer (:ddkilzer)
Comment 4 2006-07-17 21:41:01 PDT
This appears to be fixed now.  Tested with a locally-built r15495.  Going to mark it a duplicate of Bug 9642. *** This bug has been marked as a duplicate of 9642 ***
David Kilzer (:ddkilzer)
Comment 5 2006-07-18 04:15:40 PDT
NOTE: I filed Bug 9982 for the blue/green background that appears in the test case on WebKit nightly builds.
David Kilzer (:ddkilzer)
Comment 6 2006-07-18 04:31:04 PDT
Bug 9984 is also related (I found an assertion failure working with the test case from this bug).
Note You need to log in before you can comment on or make changes to this bug.