Bug 236393
| Summary: | KeyEvents are limited to one per render frame | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Michael Feldstein <msfeldstein> |
| Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | msfeldstein |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Michael Feldstein
Safari limits text input to one keypress per frame and queues up the rest, while chrome will send all pending keypresses in the next frame. So if you have any performance issues while typing quickly it will coalesce into extremely poor performance.
In the codepen, if you open it in chrome and bash keys you'll see that it keeps up with your typing, but if you do the same in safari, the events will come in one at a time and the backlog will create coalescing performance issues.
https://codepen.io/msfeldstein/pen/gOXmPWL
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
*** This bug has been marked as a duplicate of bug 226954 ***