Hi Yoav, In general it would be much easier to have a discussion if you could refer to a specific narrowly-focused bug in your email. Just saying that an area is generally broken it's hard to understand what specific aspect you're talking about.
So: What exact functionality is broken, and how do you propose to fix it? Also, I think there are currently many more important (and far easier) bugs in Chrome/WebKit around BiDi support, perhaps it would make sense to look at those first. Some notable low hanging fruit: https://bugs.webkit.org/show_bug.cgi?id=3710 - Directional caret support. https://bugs.webkit.org/show_bug.cgi?id=19785 - Select doesn't work right for dir=rtl. So to try to address your email: Chrome has (to my knowledge) 2 types of controls: 1) Native OS controls - OmniBox, the Find bar, etc. 2) Controls drawn by WebKit - basically all controls that are part of a Web Page. Regarding #1 - Native OS controls: Keep in mind that there are platform conventions for how native controls behave, I'd be concerned with confusing users. Regarding #2 - WebKit controls: While there are still some open bugs around caret movement and drawing in WebKit controls, much of the current behavior reflects explicit design decisions. If you think this functionality is broken, it might be good to look at the WebKit bug database to see if there's already a bug open around the issue you want to fix. If there is you might want to leave a comment in the bug with a proposed fix. A final thought: Getting BiDi cursor movement correct is non-trivial, there are no standards in this area and many corner cases. Best regards, Jeremy On Tue, Jun 2, 2009 at 2:47 AM, nakro <[email protected]> wrote: > > Hi, > > this post will only make sense to those who speak hebrew or arabic > as you know, the selection in windows of text in a mixed hebrew > english text is at best a joke > nobody understands it natively, and the cursor (caret in windows > jargon) movement is > also very awkward (right goes left, left goes right.... you know what > i mean) > > my point is this > if i get it right (i did debug chrome for the last 2 weeks) > you seem to have written your own controls, > so why not do it right this time for the entire arab/hebrew world ? > > since you anyways use UTF16 and you it has all the "chars" neccessary > (the change direction > and pop direction and the like) > > wouldn't it be great if chrome would make RTL the way it should have > been ? > > i would be happy to do it myself, i have all the knowledge to do it in > windows > but i, of course, am still kinda new to chrome so i would prob need > some help in doing it > > also, if you like this idea, there needs to be someone who can help me > with the arabic part > > this is a huge task, to be sure, but i think it would be worth doing, > especially that the hebrew support in windows > has been really bad for years (don't know how mac/linux handle it) > > so any thoughts will be welcome, you can also say "NO, Thank you" and > that would also be cool > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
