Issue metadata
Sign in to add a comment
|
Cursor position text stuck at 0 position after selecting text in chrome extension web accessible resource loaded in iframe if its parent element is scrollable
Reported by
tobias.c...@gmail.com,
Sep 17
|
||||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36
Steps to reproduce the problem:
SETUP:
1. Unzipp the provide cursor-reset.tgz
2. Load ./cursor-reset/extension directory in chrome as unpacked extension
3. Update backwards_parent.html to reference the installed extension id
4. Serve backwards_parent.html from webserver e.g. by running the following in the base folder:
cd ./cursor-reset && python -m SimpleHTTPServer 9991
5. Load http://localhost:9991/backwards_parent.html in chrome
REPRODUCTION OF BUG:
1. On the loaded page [http://localhost:9991/backwards_parent.html] notice there are two iframes each with their own text field.
2. Type into the input of the second iframe some text e.g. 'abcdef'.
3. Position the cursor over the text on the right hand side (e.g. right after the 'f').
4. Click and drag the cursor to the beginning of the text, this should highlight the text as expected.
5. Start typing '123456' this will replace the highlighted text as expect HOWEVER the cursor is stuck at the beginning of the input,
thus you end up writing '654321'
What is the expected behavior?
The cursor should behave properly and stay at the end of the text you have typed.
What went wrong?
The cursor of the <input type="text"/> element becomes stuck at the beginning and causes any typed text to be entered backwards.
Did this work before? Yes 67.0.3396.79
Does this work in other browsers? Yes
Chrome version: 68.0.3440.84 Channel: stable
OS Version: OS X 10.12.5
Flash Version:
-- The setup of this bug shows two iframes. The first is hosted straight from the webserver, the second is hosted from
the chrome extension. The bug only appears to affect the iframe hosted from the chrome extension.
-- The bug also only appears to show up when the parent element of the input text is scrollable.
,
Sep 18
Tried testing the issue on mac 10.13.3 using chrome reported version #68.0.3440.84 as per comment #0. Attached a screen cast for reference. After performing the set up and loading http://localhost:9991/backwards_parent.html generated 2 iframes, out of which the iframe hosted straight from the webserver had a text field where as the second iframe hosted from the chrome extension did not load. tobias.carson@ - Could you please check the attached screen cast and please let us know if anything missed from our end. A screen cast from your end will be much helpful in triaging the issue further from our end. Thanks...!!
,
Sep 18
I think I know why its not loading. It looks like the backwards_parent.html was not updated to reflect the new chrome extension ID. Inside the backwards_parent.html there is <iframe src="chrome-extension://bhjanmjhgdekaepeafgkoonkcgmkmlep/backwards.html" style="height: 100px; width: 100%"></iframe> That ID bhjanmjhgdekaepeafgkoonkcgmkmlep needs to be replaced with the installed ID: from the video this looks to be epfblmbhcbenhakdojcgpjdekfiglgbc. I appreciate the followup, hopefully this helps. Thanks, Tobias
,
Sep 18
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 19
Able to reproduce the issue on Mac 10.13.3, Win-10 and Ubuntu 14.04 using chrome reported version #68.0.3440.84 and latest stable #69.0.3497.100 but the same is not reproducible in the latest canary #71.0.3555.0 and latest beta #70.0.3538.16. Reverse Bisect Information: ===================== Good build: 70.0.3538.15 Bad Build : 70.0.3538.14 Change Log URL: (From omahaproxy) https://chromium.googlesource.com/chromium/src/+log/70.0.3538.14..70.0.3538.15?pretty=fuller&n=10000 From the above change log suspecting below change Change-Id: Id9d4bb6bdb6a3fa33b4e15af35a0588e952755fe Reviewed-on: https://chromium-review.googlesource.com/1197409 kenrb@ - Could you please check and merge the fix to M-69 if it is a valid candidate. Adding label RBS as it seems to be a recent regression. Thanks...!!
,
Sep 19
This is a dupe of issue 876662 . The regression was in Chrome 68, and this was considered critical enough to merge to Stable branch. I don't know if there will be any respins of 69 at this point in any case. The fix is in Chrome 70. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by susan.boorgula@chromium.org
, Sep 17