(No comment was entered for this change.)

(No comment was entered for this change.)

I haven't tried yet, but Hironori fixed a similar  issue 3523  for Windows before.

The bug seems to be that the cursor position is wrong. This is Linux specific. Thanks 
to Markus for guiding me though setting up Thai input.

I'll take a look, but if one of the i18n folks wanted to fix it first, I wouldn't be 
too upset ;)

agl,

To investigate this issue quickly today, it seems your Font::selectionRectForComplexText() returns a wrong position 
for LTR strings.

604:    if (toX == -1 && !to)
605:        toX = rightEdge;
606:    else if (!walker.rtl())
607:        toX += truncateFixedPointToInteger(toAdvance);

This code adds |toAdvance| to |toX| when the given text is LTR. Even though I'm not totally sure about this code, 
I'm wondering if it is correct to add |toAdvance| to |toX| here for LTR strings. (As far as I tested this function 
with some LTR strings, |toX| becomes the correct value before reaching to this code.)

Since I'm not sure the context of this code, it is better for you to fix this problem. Anyway, I'm happy to help 
you if you need my help.

Regards,

(No comment was entered for this change.)

This problem maybe cause of this case,too.
1. put cursor on "กูเกิล|"
2. drag to select to "|กูเกิล"
3. copy and paste result is "กูเกิ"

it missing the last character 

(No comment was entered for this change.)

Unassigning from me. The patch is pretty small if anyone cares to land it: 
https://bugs.webkit.org/show_bug.cgi?id=28284

 Issue 22981  has been merged into this issue.

(No comment was entered for this change.)

Hello. What is that mean Mstone-X ?

It just means this will likely not be fixed in the next few weeks. I am trying to make sure 
we have all the bugs sorted so we can properly allocate them into buckets when we 
organize our milestones. 

"not be fixed in the next few weeks" bad news.  T^T. But thank you for your update.

(No comment was entered for this change.)

suteanfx,

Sorry for my slow update.
Let me clarify the meaning of "not be fixed in the next few weeks".

Fortunately for you, we (evan and eseidel) have landed a fix for this issue. So, I 
think this issue is "fixed" if you get the latest snapshot of Chromium from our build 
server and use it.

(*1) http://build.chromium.org/buildbot/snapshots/chromium-rel-linux/

On the other hand, we would like to leave this issue open because we are writing an 
automated test for this issue now.

Regards,

(in reply to comment 15),

TextInputController.firstRectForCharacterRange() returns the pixel-level rectangle for the specified character range. So, to use 
this function, we can write a layout test for this issue.
Unfortunately, this function is implemented only by Mac WebKit, i.e. the Chromium test_shell doesn't implement this function. So, 
we need to implement the function for the Chromium test_shell and write a layout test for this issue.

I have filed another WebKit issue to track the status of its layout test: <https://bugs.webkit.org/show_bug.cgi?id=30902>.

Regards,

 It fixed! 4.0.229.0 (30549) :)

(No comment was entered for this change.)