On 12/13/07 3:32 AM, "Alexey Proskuryakov" <[EMAIL PROTECTED]> wrote:
> In the latest WebKit nightlies, we have changed keyboard event > handling to match Internet Explorer much more closely. This has fixed > some compatibility bugs, although it remains to be seen whether > significant problems with WebKit-specific content will be uncovered. > It is entirely possible that we will need to undo some or all of these > changes at some point. > > Conceptually, the changes all have a single root cause. We now > treat keydown as an event corresponding to a physical key press which > hasn't been translated with a keyboard layout yet - and keypress > corresponds to a character being typed. Of course, we continue to > support textInput as a more modern text event suitable for > international input. > <snip> > - WBR, Alexey Proskuryakov > Do these changes - at least the ones not directly related to text input - apply only to read-only areas? At first glance (talking Mac here), it still appears that a TSMDocumentID is created for read-only areas. Should I be expecting changes to the way text input (from an input method, at least) is handled as well? A brief test with my input method crashed in -[WebHTMLView(WebNSTextInputSupport) attributedSubstringFromRange:] when sending an OffsetToPos. Anyway, looks like I've got a bunch of testing to do... Thanks, Evan Gross -- Evan Gross, President, Rainmaker Research Inc. Developers of Macintosh and Windows Software Spell Catcher for Mac OS and Windows http://www.rainmakerinc.com/ _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo/webkit-dev
