RESOLVED WORKSFORME 66197
Missing content on expresslane.apple.com 
https://bugs.webkit.org/show_bug.cgi?id=66197
Summary Missing content on expresslane.apple.com
webkit
Reported 2011-08-13 18:35:30 PDT
Steps to reproduce: 1) Go to https://expresslane.apple.com/Symptoms.do 2) You will be redirected to https://expresslane.apple.com/GetproductgroupList.do 3) Choose iPhone, then Non-Technical Questions, then Continue 4) The buggy page https://expresslane.apple.com/Symptoms.do will load (it will be headed Issue Description) 5) There will be hardly anything there. This is the buggy page. Actual Results: Hardly anything loaded. Expected Results: Some text, images and forms should have loaded. Build Date and Platform: Occurred in Build r92990 on 2011-08-14 on Mac OS 10.7 Additional Builds and Platforms: Also occurs in Build r93015 on 2011-08-14 on Mac OS 10.7
Attachments
Picture of page not working in WebKit (127.58 KB, image/png)
2011-08-13 21:43 PDT, webkit 		no flags
Details
Picture of page working in Firefox (169.56 KB, image/png)
2011-08-13 21:44 PDT, webkit 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
webkit
Comment 1 2011-08-13 21:43:28 PDT
Created attachment 103873 [details] Picture of page not working in WebKit
webkit
Comment 2 2011-08-13 21:44:20 PDT
Created attachment 103874 [details] Picture of page working in Firefox
Alexey Proskuryakov
Comment 3 2011-08-15 14:34:37 PDT
I cannot reproduce this with r92990 or r93043 nightly builds on Mac.
webkit
Comment 4 2011-08-19 02:50:28 PDT
It is still malfunctioning for me even in r93384. (In reply to comment #3) > I cannot reproduce this with r92990 or r93043 nightly builds on Mac.
Alexey Proskuryakov
Comment 5 2011-08-19 08:46:53 PDT
Do you have any Safari extensions installed? Will this still happen for you if you disable extensions via Safari preferences? Will this still happen if you delete all apple.com cookies via Safari preferences (Privacy tab)?
Sal
Comment 6 2014-01-20 23:46:46 PST
Cannot reproduce with r162366
Note You need to log in before you can comment on or make changes to this bug.