RESOLVED INVALID 50355
scrollBy() script does not work in Android version of Chrome browsers
https://bugs.webkit.org/show_bug.cgi?id=50355
Summary scrollBy() script does not work in Android version of Chrome browsers
Keith Shaw
Reported 2010-12-01 15:26:55 PST
DESCRIPTION OF PROBLEM I am developing an html-based story reader interface that has paged content. See demo: http://www.ipulpfiction.com/books/_bookReader/reader/pagedDEMO.html The page works well in the desktop version of Chrome running under Mac OS & Windows, but we are targeting tablet audience and the Android version of the Chrome browser does not seem to support scrollBy( ). This is a bug in webkit. The iOS version of Safari had the same problem, which Apple fixed for us in the latest version of iOS 4. NOTE: our Android testing device was a Samsung Galaxy Tab. Oddly enough, the scrollBy( ) functions works (albeit incorrectly) on GoogleTV. STEPS TO REPRODUCE 1 Go to: http://www.ipulpfiction.com/books/_bookReader/reader/pagedDEMO.html 2 Click on a margin to hide the cover. 3 Click on the right margin to advance the page WORKS FINE in the desktop version, DOES NOT WORK advance in Android. Here's the underlying process: The contents of an iFrame ('storyFRAME') is being manipulated. <iframe src ="text.html" width="440" height="660" id="storyFRAME" frameborder="0" scrolling="no" ></iframe> I'm scrolling the content of an iFrame with the following javascript: onClick="document.getElementById('storyFRAME').contentWindow.scrollBy(460,0)" iFrame Source URL: http://www.ipulpfiction.com/booksDEV/BlackMask01-1/book_BM011r4orgthx/text.html CSS of <div> on the iFrame Source URL: #story { height:660px; position:absolute; top:0; left:0; -moz-column-width: 440px; -moz-column-gap: 5px; -webkit-column-width: 440px; -webkit-column-gap: 5px; column-width: 440px; column-gap: 5px; }
Attachments
Alexey Proskuryakov
Comment 1 2010-12-02 11:33:45 PST
Android WebKit isn't built from webkit.org sources directly, so we cannot track its bugs here. Closing as INVALID per our policy. Please report this via <http://source.android.com/source/report-bugs.html>.
Note You need to log in before you can comment on or make changes to this bug.