Why is this important? Because the ability to distinguish between a user initialized action and a scripted one can make the difference to optimize the UI.
Continue reading Event.isTrusted property from UI Events shipped in Chrome 46
I found this weird bug in Chrome for Android: in a content editable, using a keyboard with autocorrect capabilities such as the Google Keyboard or SwyftKey etc, the marking of the current word, made with an underline is left behind when the user taps different elements.
Continue reading Chrome leaves the autocorrect underline when tapping on different elements in a content editable element
While debugging some issues with lost of formatting in mobile editors I started researching about how to control input methods in mobile devices: we can control how the user gets corrected for words, autocorrection and spellchecking.
This feature is often desirable, however it causes content-loss in a rich text editor environment.
Continue reading Autocorrect, autocapitalize and autocorrect in contenteditable
When we work with text editors we need to listen to every single event happening at the keyboard level and then act accordingly. For example after typing a space we might need to transform a link-like text into an actual link.
While this feature has been working fine in all the devices, our QA team has found an issue with this component, and digging into the code I found how the space is not being recognized correctly as a space.
Continue reading Android Webview – The space event is not firing as expected