|Summary:||Cannot work within MobileMe with WebKit|
|Product:||WebKit||Reporter:||Thorsten Zoerner <mail>|
|Component:||New Bugs||Assignee:||Nobody <webkit-unassigned>|
|Severity:||Normal||CC:||jorge, mitz, pvollan, r_J_baker, ronman, wambrose, wruss714, xfodder|
|Version:||528+ (Nightly build)|
|OS:||OS X 10.5|
Description Thorsten Zoerner 2008-07-11 05:34:17 PDT
Using Webkit nightly 3.1.2 (5525.20.1) I am able to access the new MobileMe service from Apple. That is, I can log on. However when I try to press any button on the top for "Calendar", "Address Book" and such, WebKit will stall and not proceed with a new screen. With Safari - "About Safari" gives me exactly the same version number as above, which I don't understand - it works in a few seconds.
Comment 1 Gavin Sherlock 2008-07-11 07:28:43 PDT
I can't get anything to happen at me.com after logging in either. Tested with r35113 on 10.5.4. Don't know if this is me.com or Webkit though.
Comment 2 Gavin Sherlock 2008-07-11 11:28:24 PDT
It does work in release safari on 10.5.4, so this is a regression, and should be marked as such (I don;t have the power to classify as a P1, or change the title).
Comment 4 Thorsten Zoerner 2008-07-11 12:49:58 PDT
Changed priority to P1 according to Gavin's e-mail.
Comment 5 Mark Rowe (bdash) 2008-07-11 15:53:05 PDT
The underlying issue here is outside of WebKit. The issue will be tracked via the associated Radar. Thanks for the bug report.
Comment 6 mitz 2008-07-11 23:11:51 PDT
*** Bug 20015 has been marked as a duplicate of this bug. ***
Comment 7 Matt Lilek 2008-07-12 09:16:18 PDT
*** Bug 20017 has been marked as a duplicate of this bug. ***
Comment 8 Matt Lilek 2008-07-12 11:11:59 PDT
*** Bug 20019 has been marked as a duplicate of this bug. ***
Comment 9 Mark Rowe (bdash) 2008-07-12 16:18:54 PDT
*** Bug 20024 has been marked as a duplicate of this bug. ***
Comment 10 Mark Rowe (bdash) 2008-07-12 16:20:08 PDT
*** Bug 20021 has been marked as a duplicate of this bug. ***
Comment 11 Mark Rowe (bdash) 2008-07-14 14:20:57 PDT
My testing shows that this bug has now been fixed.
Comment 12 Robert Blaut 2008-07-16 22:42:09 PDT
*** Bug 20071 has been marked as a duplicate of this bug. ***
Comment 13 Robert Blaut 2008-07-17 10:36:14 PDT
*** Bug 20082 has been marked as a duplicate of this bug. ***