Here's my issue: I've created a short story publishing, distribution site ( http://www.iPulpFictiuon.com ) aimed at TABLET USERS. I've also developed an HTML 5/CSS 3 based e-reader, which is designed for and optimized to webkit's implementation of HTML 5 / CSS 3. It currently works perfectly in the desktop versions Chrome, and Safari. You can view a sample here: http://www.ipulpfiction.com/books/_book ... sGame.html My HTML 5 / CSS 3 multi-column styles were implemented, but the javascript did not execute in the MOBILE versions of webkit browsers: function pageScrollNEXT() { storyFRAME.contentWindow.scrollToBy(440,0); } It was easy to contact and work with Apple. The problem was fixed in MOBILE Safari with the release of iOS 4.2. I have tested every tablet device using a webkit-based mobile browser, the latest being on the XOOM, and found the same error. Since the exact same error occurs in the Android mobile browser and in the Palm Emulator SDK 1.4.5.465, I suspect that the root problem is in the javascript implementation in the underlying mobile webkit code. Apple apparently didn't migrate the fix in iOS 4.2 down or though the webkit food chain. I've reported this to Android and WebOS, with no reply. To whom do I need to talk to get this bug addressed across the webkit ecosystem? I would like actual contacts as I am having trouble identifying who to talk to. I want our eReader to work in ALL webkit browsers. Thanks in advance for your help
> It was easy to contact and work with Apple. How did you communicate with Apple? Can you find a seven digit Radar number for your bug report? Generally speaking, bugs that only occur on Android should be reported to Google, and not here, because Android WebKit isn't built directly from webkit.org sources.
(In reply to comment #1) > > It was easy to contact and work with Apple. > > How did you communicate with Apple? Can you find a seven digit Radar number for your bug report? > > Generally speaking, bugs that only occur on Android should be reported to Google, and not here, because Android WebKit isn't built directly from webkit.org sources. Thanks for your reply and any future assistance. I contacted Apple Developer Technical Support via email. I just sent them the following message: ----- Follow-Up: 120985259 A while ago, you helped resolve a javascript issue in the mobile version of Safari. I am now trying to work with other platforms that use webkit, including the webkit org, Android, and WebOS, so they can address the same issue. Alexey Proskuryakov <ap@webkit.org> at webkit asked: "Can you find a seven digit Radar number for your bug report?" My case number is 9 digits. Is this what he needs? Since webkit is an open source project, would you be able to send me a description of the fix so I can pass it on to the other development groups? Thank you for all your help, Keith Shaw, Publisher iPulpFiction.com ---- I hope I can get you the info you need. Unfortunately, I can't pin-point a contact on Android. I have heard back from someone in the WebOS community, who is helpful and suggested a CSS alternative to the scrollBy() function that I will explore. Thanks again.
Thank you! I think that the best course of action now is to file an Android bug at <http://source.android.com/source/report-bugs.html>. I'll close this bug for now, but we can re-open it if Apple DTS responds with details indicating that it's a issue that should be tracked at webkit.org.