RTL (right-to-left) keyboard navigation in an HTML <TextArea> -

After

I'm working with some HTML which includes a & lt; Text area & gt; . Currently, I am testing the input of the characters of LTR and RTL , such as "abc أبج ABC" .

  & lt; Div class = "mycomment" dir = "RTL" & gt; & Lt; Form method = "get" action = "{$ self}" & gt; & Lt; Input type = "hidden" name = "id" value = "{$ entry}" /> & Lt; Textarea name = "comment" class = "commentarea" /> & Lt; / Textarea & gt; & Lt; Br / & gt; & Lt; Input class = "button" type = "submit" value = "{$ postlink}" /> & Lt; / Form & gt; & Lt; / Div & gt;  

The string performance is correct when occurs in RTL mode, however, keyboard navigation is incorrect, especially when it does not follow the correct sequence of English and Arabic strings are going through sections.

Any ideas how can I bypass or be able to solve this problem? Unfortunately, keyboard navigation is probably "true" according to specifications.

When trying to run through mixed-direction words, keyboard shortcuts such as Ctrl + > , to jump from word to word, direction based on the direction of characters Start changing The cursor's current state - Instead of treating the entire string as a one-directional form of navigation.

This makes sense, however, when you consider that the keystrokes in typing in computers all the other mixed-mode sentences

If you start typing the LTR characters, then you expect that they will go from left to right (with each subsequent character appearing on the right) You start typing rtl characters, then you expect them to travel right-to-left (to the left of the last part of each of the previous characters).

Think about it like this:

Ctrl + > means "one word is not correct" - its The word " next " left - em> next is related to the order, in which bytes are organized in memory, but rather related to the order, in which they < / Em> are displayed on the screen. A word starts at the right or left of the screen, characters are organized in memory sequentially, starting with the beginning of the word, and ending with the end of the word

In other words:. Exhibit-order instead of Ctrl + byte-order .

Then travel in - back to your question of how to overcome it ...

Unless you work within keyboard navigation, a lot to change There were no good ways to "fix" your box, to write complex JavaScript (which includes its own set of challenges and troubles). However, you can try the following options, if you think it will negatively impact your customers:

1. Provide training Bidding inside and outside Learn the tricks of the keyboard, and teach your users. (I know, I know, there is a lot of work and you do not have time / budget).
2. Trust your users If your users have mixed code LTR and RTL text their Em> In the application, there is nothing that regular other application means that they are probably used for this set of problems because it is a Standard is a set of issues if they do so - maybe they are already working, whose They used to be - and you changing it fix it actually injury their productivity
3. Document it , and submit feature request . If you believe that something given has to be implemented browser or vendor (like Microsoft) differently, your user must be active in the community and updates, patches And in addition to the convenience, the software world gets better - and it does not burden you completely on your organization - or worse - on worse