Bug 153872 - REGRESSION (Safari 9.0.2?): Nested contenteditable scrolls outer window on horizontal select
Summary: REGRESSION (Safari 9.0.2?): Nested contenteditable scrolls outer window on ho...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: Safari 9
Hardware: Mac OS X 10.11
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2016-02-04 10:16 PST by m.lewandowski
Modified: 2022-06-02 12:13 PDT (History)
7 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description m.lewandowski 2016-02-04 10:16:07 PST
1. Open a demo: https://jsfiddle.net/fpua774e/
1. Try to select any part in "Try to select some text" text. It's preferable to make a selection horizontally, e.g. from left to right (vertical scroll should not be triggered at all in this case).

**Expected:**

Text is selected.

**Actual:**

Browser goes crazy with vertical scrolling.


I'll just add that CKEditor customers reported this bug to us, and it's a critical bug that makes using CKEditor impossible in Safari (see http://dev.ckeditor.com/ticket/14314).
Comment 1 Radar WebKit Bug Importer 2016-02-06 12:51:46 PST
<rdar://problem/24540046>
Comment 2 Simon Fraser (smfr) 2016-02-12 11:35:14 PST
Does this still happen in nightly builds?
Comment 3 m.lewandowski 2016-02-13 03:49:40 PST
I can check it on Monday, as currently I don't have any mac nearby. Nonetheless you can always check it in demo that I've attached.
Comment 4 m.lewandowski 2016-02-15 06:33:45 PST
Checked just with the latest nightly, and it's not fixed.
Comment 5 Alex Jarvis 2016-03-07 15:56:09 PST
This seems to be fixed in 9.1 which is in the 10.11.4 betas.
Comment 6 Ahmad Saleem 2022-06-02 12:13:19 PDT
I am unable to reproduce the issue using mentioned JS Fiddle in Comment 01 using Safari 15.5 on macOS 12.4. It matches also with Chrome Canary 104. Although for Firefox Nightly 103, iframe does not show any text at all.

From the expected result, the bug was that text selection was an issue, which is no longer the case. I think this can be closed as "RESOLVED CONFIGURATION CHANGED" but in case Firefox behaviour is correct and <iframe> should not have any text then we can open separate bug using the test case from Comment 1 and also raise similar in Blink on Chrome side.

Please update accordingly. Thanks!