Bug 154289 - Wrong / blocked cursor position
Summary: Wrong / blocked cursor position
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: UI Events (show other bugs)
Version: Safari 9
Hardware: Mac OS X 10.11
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-16 09:16 PST by Marco Liceti
Modified: 2016-02-16 09:16 PST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marco Liceti 2016-02-16 09:16:43 PST
Hi, I'm a web developer using the latest Macbook, with the retina 12" display. When writing with the Atom text editor or inside some web pages I experience some weird behaviors that I can only explain in one way: when I select text and then quickly start typing, the cursor stays blocked (or maybe just jumps to a wrong position). In some places (e.g. Google search box), this may leave with the impression of typing backwards. In general, after text selection, I have to wait before starting to type, otherwise I'll mess with the current text. It seems that similar issues are very common, mostly (but not only) on Mac Os X devices with retina displays. I tried several proposed fixes: reset PRAM, disable hardware acceleration, reset default font size, etc.. Nothing seems to work. I'm reporting this issue here because I noticed that those behaviors only happen with webkit-related products (Chrome, Safari, Atom, Opera), but not with Firefox. My guess is that the culprit is a bad implementation of the mouseup event. Maybe it's just slow, or maybe it's messing with keyboard events. Or both. I don't know. Hope you can reproduce and fix this. Thank you.