Last modified: 2014-09-03 17:18:15 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 T68339, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 66339 - VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks connected Arabic letters
VisualEditor: In WebKit, moving the cursor (caret) with the arrow keys breaks...
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!
: i18n
Depends on:
Blocks: ve-multi-lingual ve-nonenglish
  Show dependency tree / graph
 
Reported: 2014-06-08 07:53 UTC by Amir E. Aharoni
Modified: 2014-09-03 17:18 UTC (History)
7 users (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Amir E. Aharoni 2014-06-08 07:53:19 UTC 
To reproduce:
1. Edit an article in Arabic.
2. Move the caret forward using the arrow keys.

Observed: The Arabic letters next to which the caret moves are disconnected.

Expected: Moving the caret must only move the caret. It must not change the appearance of the text.

This works well in Firefox, but broken in Chrome.
Comment 1 Amir E. Aharoni 2014-08-27 13:27:47 UTC 
I am not sure what fixed it, but it works for me now in Chrome 36.0.1985.143 on Fedora 20.

Can this be tested automatically to prevent regression?
Comment 2 Krinkle 2014-08-27 13:42:53 UTC 
Be sure to also test in a recent version of Safari (which runs on WebKit).

Chrome hasn't been based on WebKit for almost 2 years now. It's using Chromium/Blink instead.
Comment 3 Amir E. Aharoni 2014-08-27 13:44:48 UTC 
Well, I reported it, and I only have Chrome on Linux, so I guess I meant "Chrome" or "Blink" and not "WebKit".
Comment 4 Krinkle 2014-08-27 13:48:02 UTC 
(In reply to Amir E. Aharoni from comment #3)
> Well, I reported it, and I only have Chrome on Linux, so I guess I meant
> "Chrome" or "Blink" and not "WebKit".

If it was present in Chrome at that point in time though, depending on whether it was a recent regression in Chrome, it likely still exists in WebKit/Safari (since Blink is a fork of WebKit).
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links