RESOLVED INVALID 38053
scroll event never fired on Webkit on iPhone OS 4 beta 2 with webkit AppleWebkit/532.9 
https://bugs.webkit.org/show_bug.cgi?id=38053
Summary scroll event never fired on Webkit on iPhone OS 4 beta 2 with webkit AppleWeb...
Sven Haiges
Reported 2010-04-23 11:36:45 PDT
Overview: It seems the window scroll Event never gets fired on iPhone OS 4 beta 2 (it works on beta 1) and the webkit that is installed on this OS by default. I have provided a very simple testcase that demonstrates this. Steps to Reproduce: <html> <body onload="window.addEventListener('scroll', function(){alert('scroll');}, false);"> I love webkit but need a scroll event, please! </body> </html> This simple html page with alert with each scroll on iPhone OS 4 beta 1, but it will stop working on beta2. It also works on older versions of iPhone OS and their webkit based browsers. It must have been introduced just recently. Actual Results: On iPhone OS 4 beta2, showing a apple webkit version of 532.9, scrolling the page results in no alert dialog being shown. Expected Results: One should see an alert box which says 'scroll'. Build Date & Platform: WebKit/Safari part of iPhone OS 4 beta 2. Please note this used to work on beta1 and former versions.
Attachments
Add attachment proposed patch, testcase, etc.
Mark Rowe (bdash)
Comment 1 2010-04-23 16:07:05 PDT
Two comments: 1) Prerelease Apple software is covered by NDAs. It’s not appropriate to discuss it in a public forum such as this. 2) Bugs specific to WebKit on iPhone should be reported at <http://bugreport.apple.com/> as iPhone WebKit is not built directly from the webkit.org codebase. Due to point 2) I’m going to close this as INVALID and ask that you file this at <http://bugreport.apple.com/> instead.
David Kilzer (:ddkilzer)
Comment 2 2010-04-23 16:23:32 PDT
<rdar://problem/7902085>
David Kilzer (:ddkilzer)
Comment 3 2010-04-23 16:24:07 PDT
(In reply to comment #1) > Due to point 2) I’m going to close this as INVALID and ask that you file this > at <http://bugreport.apple.com/> instead. I pulled it into Radar as <rdar://problem/7902085>.
Note You need to log in before you can comment on or make changes to this bug.