This should be fixed now. We had to do some fancy (hacky) stuff to make it work, but getCursorPos() should return the correct value now. The problem is that IE automatically trims newlines off the end of the selected text, making it difficult to know exactly how many characters are selected. Now, we move the cursor back 1 character at a time, which allows us to figure out how many \r\n are being truncated.
Thanks, John LaBanca [email protected] On Tue, Jul 28, 2009 at 10:26 AM, Joel Webber <[email protected]> wrote: > I believe John committed several fixes to TextBoxImplIE6 recently, and it > looks like this patch might not apply any more. Have a look at the source > here to see if you think it still makes sense: > http://code.google.com/p/google-web-toolkit/source/browse/trunk/user/src/com/google/gwt/user/client/ui/impl/TextBoxImplIE6.java > > > On Mon, Jul 27, 2009 at 6:00 PM, lkcl <[email protected]>wrote: > >> >> folks, hi, >> >> as you know, pyjamas tracks GWT fairly closely, with the UI widget API >> being near-identical to that of GWT, and even to the point where i >> wrote a java2py.py script which converts GWT java code [mostly] to >> python, to make the process of porting GWT widgets over to python that >> much easier. we even copy over the platform overrides with the >> Javascript sections, wholesale. >> >> on very rare occasions, we encounter bugs before you do :) >> >> i was wondering therefore if you've encountered this: >> >> http://code.google.com/p/pyjamas/issues/detail?id=205 >> >> your thoughts appreciated. >> >> l. >> >> >> > --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
