New issue
Advanced search Search tips

Issue 880606 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 876662
Owner:
Closed: Sep 5
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug-Regression



Sign in to add a comment

Replacing highlighted input text in an iframe with a scrollbar causes text to be entered backwards

Reported by tovin.hu...@gmail.com, Sep 4

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.81 Safari/537.36

Steps to reproduce the problem:
1. Create a simple page with an input and some content that will make the page tall enough to see a scroll bar when included in a frame

2. Create a page with a frame that uses the page from Step 1 as the src.

3. Be sure that the iframe height is such that there is a scrollbar

4. Highlight existing text in the input using the mouse. Start from the right of the text and drag to select it all and let go outside of the frame or browser window to the left

5. Start typing to replace the highlighted text

What is the expected behavior?
The text is entered in the order that it is typed and the input cursor line will be blinking

What went wrong?
The text is entered in reverse order and the input cursor line is solid

Did this work before? Yes 67.0.3396.79

Chrome version: 69.0.3497.81  Channel: stable
OS Version: 10.0
Flash Version: 

I noticed the behavior on version 68

You can reproduce it with this simple page:
http://s3.amazonaws.com/typing-backwards-issue/iframe.html
 
Backwards text.PNG
2.0 KB View Download
The src of the frame must be on a different domain than the parent page
Cc: pbomm...@chromium.org
Labels: Needs-Triage-M69
I see similar behavior on 68.0.3440.106 as mentioned by  tovin.hudson@, tagging bug with Needs-bisect and apply appropriate labels once we have the culprit. 
Components: Internals>Sandbox>SiteIsolation
Mergedinto: 876662
Owner: kenrb@chromium.org
Status: Duplicate (was: Unconfirmed)
Thanks for the report!  This looks like a duplicate of  issue 876662 , which kenrb@ just fixed in 71.0.3539.0.

Indeed, I can repro the bug in 69.0.3497.81 but it's working correctly in 71.0.3542.0.  (Ken, let me know if that's incorrect, though!)
That's correct, this is the same bug.

Sign in to add a comment