Issue metadata
Sign in to add a comment
|
Scrolling issues with iframes and contenteditable=true
Reported by
oleg.kli...@team.wrike.com,
Oct 23 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.62 Safari/537.36 Steps to reproduce the problem: 1. Go to https://jsfiddle.net/1wwjtgwz/ 2. Copy the text inside the box 3. Paste the text back to the box once or twice - second scrollbar should appear. 4. Scroll down to the end of text. 5. Try to type something at the end of the text. What is the expected behavior? Outer container scroll position is not changed; caret is still visible to user. Moving caret up and down changes scroll position of both inner and outer container so the caret remains visible to user. What went wrong? Outer container scroll position is reset to 0. This will happen even when some text is deleted and iframe scrollbar disappeared. Moving the caret up and down does not change scroll position of the outer container. Did this work before? Yes 59 or 60 (not sure) Does this work in other browsers? Yes Chrome version: 62.0.3202.62 Channel: stable OS Version: Flash Version: This behavior is encountered in Chrome 61, 62 and 63 beta. Also I noticed that everything is fine when the large text is not pasted, but added programmatically.
,
Oct 24 2017
I've got some additional information about this bug. 1) The bug happens only when copy-pasted text height is larger than height of scroll area (300 px in jsfiddle example) 2) The scroll position jumps up by the height of pasted text. In case when height of pasted text is more or equal than height of iframe, scroll position jumps to the top.
,
Oct 24 2017
Able to reproduce this issue on reported version 62.0.3202.62 , on M61 - 61.0.3163.100 and on latest dev 63.0.3239.9 using Windows 10, Ubuntu 14.04 and Mac 10.12.6. But Issue is working fine in latest canary 63.0.3248.0. Manual Bisect Info: =============== Last Bad Build: 64.0.3243.0 First Good Build: 64.0.3244.0 You are probably looking for a change made after 509815 (known good), but no later than 509816 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/1c42b7a0d9771845d4d6ec9ef985eb7d0fe54f8f..6247becd3a3621eea409ea4758f70a9a4491a39e Probably fixed by https://chromium-review.googlesource.com/723132 @sunyunjia:Could you please confirm if its safe to merge to M-62 and M63? Thanks!
,
Oct 24 2017
This is a duplicate of crbug.com/774222 , which is already fixed by https://chromium-review.googlesource.com/723132 And yes, it is safe to merge to M-62 and M63. Please approve the merge request at crbug.com/774222 Thanks!
,
Oct 24 2017
Thanks! |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by manoranj...@chromium.org
, Oct 23 2017Labels: Needs-Triage-M62