ime: Don't throw error when getAutocorrectRange is empty.
Throwing an error spams the Chrome OS logs and sends crash reports to Chrome. Calling getAutocorrectRange when there's no autocorrect range is a perfectly valid use of the API (otherwise how do you know if there's an autocorrect range or not?), so it should not be an error condition. Return (0, 0) instead. Change-Id: I1062e04d8447058cae0f0888c97030019f99c265 Bug: b/149796494 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2444870 Commit-Queue: Darren Shen <shend@chromium.org> Reviewed-by:Keith Lee <keithlee@chromium.org> Cr-Commit-Position: refs/heads/master@{#816022}
Showing
Please register or sign in to comment