![]() + m_frame->coreFrame()->view()->setDelegatesScrolling(true) + if (m_frame->coreFrame()->isMainFrame()) m_frame->coreFrame()->view()->setDelegatesScrolling(true) +++ -1370,3 +1370,4 void WebFrameLoaderClient::transitionToCommittedForNewPage() a/Source/WebKit2/WebProcess/WebCoreSupport/WebFrameLoaderClient.cpp + // if (!(options & DoNotRevealSelection)) +++ -3122,2 +3122,2 bool Editor::findString(const String& target, FindOptions options) A quick workaround to make scrolling work with the Find operation is: In particular, we have an issue similar to bug 163911. However, it's not enough to make scrolling work (I'm still investigating this.). This is a preliminary patch to remove flattening for iframe. ![]() Ultimately he ends up having to use a dummy DIV and getBoundlingClientRect in order to detect the scroll position of the iframe, yuck! He can make the iframe body overflow:auto (along with html) and that works, but then is burned by bug 106133 (can't get/set the scroll position because body.scrollTop actually refers to the viewport). Simon, any chance your work on improving viewports/scrolling might help here? It seems really confusing that an iframe should behave differently from a scrollable div in this regard, and that iOS would be different from desktop Safari.ĭima tells me that the obvious work-around of putting a scrollable div inside the iframe is problematic for him because he doesn't have control of the iframe content/styling. It looks like web developers have struggled with this for awhile, and claim it got worse in iOS 8 eg:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |