Bug 40805 - Rendering of composition string with partial selection range is broken.
Summary: Rendering of composition string with partial selection range is broken.
Status: RESOLVED DUPLICATE of bug 37788
Alias: None
Product: WebKit
Classification: Unclassified
Component: Text (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-17 19:35 PDT by James Su
Modified: 2010-07-02 11:24 PDT (History)
1 user (show)

See Also:

Attachments
Correct behavior - IE 8 (4.54 KB, image/png)
2010-06-17 19:35 PDT, James Su 		no flags Details
Broken behavior - Hacked Chrome (3.51 KB, image/png)
2010-06-17 19:35 PDT, James Su 		no flags Details
Correct behavior of full selection range - Hacked chrome (2.56 KB, image/png)
2010-06-17 19:36 PDT, James Su 		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 James Su 2010-06-17 19:35:09 PDT 
Created attachment 59061 [details]
Correct behavior - IE 8

When using a composition string with a partial selection range, webkit can't render the selection range correctly. It'll be ok if the selection range covers the whole composition string.

See attached images: The first one is the correct behavior in IE 8, the second one is taken with a hacked chrome which supports the selection range in composition string (stock chrome doesn't support it). The third one is taken with the same chrome binary but with a full selection range.
Comment 1 James Su 2010-06-17 19:35:57 PDT 
Created attachment 59062 [details]
Broken behavior - Hacked Chrome
Comment 2 James Su 2010-06-17 19:36:50 PDT 
Created attachment 59063 [details]
Correct behavior of full selection range - Hacked chrome
Comment 3 Hironori Bono 2010-07-01 19:38:28 PDT 
It looks like a duplicate of WebKig Bug 37788: <https://bugs.webkit.org/show_bug.cgi?id=37788>.

Regards,
Comment 4 James Su 2010-07-02 11:24:50 PDT 

*** This bug has been marked as a duplicate of bug 37788 ***