Add https://webkit.org/b/138201 back to the Wall of Browser Bugs #19135
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
cvrebert
added a commit
that referenced
this pull request
Feb 9, 2016
Add https://webkit.org/b/138201 back to the Wall of Browser Bugs
|
I'm that commenter! Any known workarounds? This is insane, Apple needs more pressure to fix such a glaring issue. |
|
Found a workaround! This workaround is partially in angular.js but should work with any JS framework (or pure JS). On tapping an input field, I used $location.hash to jump to the field above it straight after focus, which caused the input cursor to stay where it was. If I just trigger a .blur() then a focus() about 300-400 ms after the scroll jumped, the input cursor 'reset' its position to the correct one. |
|
Interesting discovery. Probably too hacky for us to adopt though. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reverts #19119.
A commenter gave a new example where the bug still repros:
https://bugs.webkit.org/show_bug.cgi?id=138201#c6