Bug 7669

Summary: Quick Look clothing item window doesn't work @ bananarepublic.com, gap.com, oldnavy.com
Product: WebKit Reporter: Geoffrey Garen <ggaren>
Component: New BugsAssignee: Nobody <webkit-unassigned>
Status: RESOLVED WORKSFORME    
Severity: Normal CC: bugs-webkit, ian
Priority: P2    
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
Bug Depends on:    
Bug Blocks: 7670, 7671    

Description Geoffrey Garen 2006-03-08 14:44:10 PST
Pages like these render without product content:
http://www.bananarepublic.com/browse/product.do?cid=5349&pid=361832
http://www.gap.com/browse/product.do?cid=7389&pid=316359

To reproduce:
1) Browse to http://www.bananarepublic.com/browse/category.do?cid=7055
2) Click a pair of jeans for a "quick look"
3) You're taken to a page that's missing the product.
Comment 1 Geoffrey Garen 2006-03-21 10:04:32 PST
accessibleweb@gmail.com reports that this issue also arises @ oldnavy.com, although less frequently.
Comment 2 Mark Malone 2006-05-10 10:22:58 PDT
The "Quick Look" feature appears to work however clicking on the product image and not the "Quick Look" button often takes one to a page without the product.
Comment 3 Eric Seidel (no email) 2006-06-07 15:31:48 PDT
The page appears first blank in FireFox, but then successfully loads.  Safari never seems to fully load the correct page.
Comment 4 Eric Seidel (no email) 2006-07-01 02:07:34 PDT
Reloading the page in Safari will occasionally cause it to draw correctly.  Seems to be a race condition.  I would imagine it might be that they are accessing some value in javascript before a layout is done.
Comment 5 Darin Adler 2006-07-04 16:05:04 PDT
It worked correctly a few times for me -- I haven't seen a failure yet.
Comment 6 Brian Hagan 2006-11-08 11:19:30 PST
I can no longer replicate this bug with the nightly build. Can anyone else verify?
Comment 7 Brian Hagan 2006-11-08 13:03:46 PST
Odd, I can't even replicate the issue with 419.3 (10.4.8, Safari 2.0.4).
Comment 8 Andrew 2007-06-05 03:33:55 PDT
Latest nightly works for me so I'm marking the bug as such due to this and the time since last update.

Needs to be removed from the compatibility hitlist.