66115 2011-08-11 16:35:45 -0700 Gmail default view will not load. 2011-08-13 21:22:36 -0700 1 1 1 Unclassified WebKit Page Loading 528+ (Nightly build) Unspecified OS X 10.7 RESOLVED DUPLICATE 66010 http://www.gmail.com P1 Blocker --- 0 dwonda webkit-unassigned ap oldest_to_newest 450147 0 dwonda 2011-08-11 16:35:45 -0700 After going to gmail.com and being redirected to login page "https://www.google.com/accounts/ServiceLogin?service=mail&passive=true&rm=false&continue=http%3A%2F%2Fmail.google.com%2Fmail%2F%3Fui%3Dhtml%26zy%3Dl&bsv=llya694le36z&scc=1&ltmpl=default&ltmplcache=2&from=login" where you enter in your username and password, once you click on sign in, it attempts to load "https://mail.google.com/mail/?shva=1" (which is normal) it will fail and go straight back to the login page, if enough attempts are made it will display a "Safari can't display this webpage" error. Currently this is the only browser on my computer that fails to load gmail, if you are quick enough you can click on the load basic html link at the bottom right corner, and that will load fine. 450807 1 ap 2011-08-12 21:36:40 -0700 Are you seeing this with Safari/WebKit 5.1 as shipped with OS X Lion, or with a nightly from <http://nightly.webkit.org>? 450848 2 dwonda 2011-08-13 10:02:25 -0700 (In reply to comment #1) > Are you seeing this with Safari/WebKit 5.1 as shipped with OS X Lion, or with a nightly from <http://nightly.webkit.org>? The safari that came with lion works fine, I am having this issue only with the latest nightly build. 450865 3 ap 2011-08-13 11:16:23 -0700 This sounds like a duplicate of bug 66010. Could you please check if this still happens for you in r93015 nightly build? 450915 4 dwonda 2011-08-13 21:13:00 -0700 (In reply to comment #3) > This sounds like a duplicate of bug 66010. Could you please check if this still happens for you in r93015 nightly build? Wow, works perfectly now, thank you to whoever was responsible for the update! 450916 5 ap 2011-08-13 21:22:36 -0700 Thank you for confirming! *** This bug has been marked as a duplicate of bug 66010 ***