Original report: http://code.google.com/p/chromium/issues/detail?id=119666 If an iframe with scrolling=no contains a link to an anchor in the same document, we do not properly scroll to the anchor when it is clicked. This appears to be a regression from http://trac.webkit.org/changeset/106730 .
Created attachment 163670 [details] patch
Comment on attachment 163670 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=163670&action=review > Source/WebCore/rendering/RenderLayer.cpp:1793 > + if ((frameElement && frameElement->scrollingMode() != ScrollbarAlwaysOff) || (!frameView->frame()->eventHandler()->autoscrollInProgress() && !frameView->wasScrolledByUser())) { it is turning to be a long line.
Created attachment 166765 [details] Patch for landing
Comment on attachment 166765 [details] Patch for landing Clearing flags on attachment: 166765 Committed r130226: <http://trac.webkit.org/changeset/130226>
All reviewed patches have been landed. Closing bug.
Comment on attachment 163670 [details] patch View in context: https://bugs.webkit.org/attachment.cgi?id=163670&action=review >> Source/WebCore/rendering/RenderLayer.cpp:1793 >> + if ((frameElement && frameElement->scrollingMode() != ScrollbarAlwaysOff) || (!frameView->frame()->eventHandler()->autoscrollInProgress() && !frameView->wasScrolledByUser())) { > > it is turning to be a long line. An inline helper function could spread this out over multiple lines and allow a comment on each line.
> > > > it is turning to be a long line. > > An inline helper function could spread this out over multiple lines and allow a comment on each line. Nate, lets please go for it.