Last modified: 2014-02-28 23:46:53 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T64028, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 62028 - VisualEditor: Cursor skips by one character for Thai characters (expected skipping by one block)
VisualEditor: Cursor skips by one character for Thai characters (expected ski...
Status: ASSIGNED
Product: VisualEditor
Classification: Unclassified
Language (Other open bugs)
unspecified
All All
: High normal
: ---
Assigned To: Editing team bugs – take if you're interested!
:
Depends on:
Blocks: ve-multi-lingual
  Show dependency treegraph
 
Reported: 2014-02-28 00:31 UTC by Sorawee Porncharoenwase
Modified: 2014-02-28 23:46 UTC (History)
10 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Sorawee Porncharoenwase 2014-02-28 00:31:18 UTC
In Thai language, it is possible that many characters (at most 3 or 4) will be on top each other. For example, "ที่" consists of three characters: "ท", "ี", and "่". In standard textbox/textarea, including normal wikieditor, when you press left, the cursor will go left by 1 block = 3 characters in case of "ที่". However, for VE's editor, it will go left by only 1 character, making editors feel that he unsuccessfully pressed the key. More importantly, with the way VE's editor is, it opens possibility that editors, thinking that the cursor is after "่", will accidentally insert text between "ี" and "่".
Comment 1 Sorawee Porncharoenwase 2014-02-28 00:37:37 UTC
Note that VE produces the correct behavior for deleting text. For example, "ที่" requires 3 backspaces in order to delete it. It has already been correct. Just only iterating through letters that is wrong.
Comment 2 James Forrester 2014-02-28 00:42:46 UTC
Thank you very much for this bug report; it's very clear.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links