Summary: | ContentEditable=True inside of an Iframe jumps to the top of the parent window. | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Michael Snyder <michael.h.snyder> | ||||
Component: | HTML Editing | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | NEW --- | ||||||
Severity: | Major | CC: | cory, enrica, jacekbogd, m.lewandowski, simon.fraser, s, webkit-bug-importer, wenson_hsieh | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | 528+ (Nightly build) | ||||||
Hardware: | iPhone / iPad | ||||||
OS: | iOS 8.1 | ||||||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=140018 | ||||||
Attachments: |
|
Description
Michael Snyder
2014-12-16 12:29:52 PST
Same thing affects CKEditor, which makes it hard to use on iOS. Does this reproduce in iOS 10.3? I'm still seeing this behavior in the latest iOS. I actually discovered this while troubleshooting what I thought was a TinyMCE bug in Postleaf. It appears as though the frame's document.body.scrollTop value is always 0, regardless of whether or not the frame is scrolled. Then I realized you can't set an explicit height on an iframe in iOS. They seem to expand to the full height of their content. That said, I'm not sure if this is actually a Webkit bug or a side effect of iframe's on mobile Safari not accepting the height specified by CSS. It could be that TinyMCE, CKEditor, et al assume scrollTop will be a positive value when instead it stays at zero, and the libs are "fixing" the scroll position based on that value. Thanks. It would be helpful to have a URL that points to a page that reproduces this for you, rather than me trying to create one from the instructions. Created attachment 311892 [details]
Testcase
With this test case, I cannot reproduce the issue on an iPad running 10.3.
The issue also exists on iOS 11.4. You can reproduce test steps using this codepen: https://codepen.io/jacekbogdanski/pen/NMbdwz Just scroll down and click "Type here" text. It also would be great to get some updates on the issue status thus it's pretty old and it's causing WYSIWYG editors based on iframes unusable. |