Summary: | bananarepublic.com doesn't support Safari | ||
---|---|---|---|
Product: | WebKit | Reporter: | Geoffrey Garen <ggaren> |
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED FIXED | ||
Severity: | Normal | Keywords: | InRadar |
Priority: | P2 | ||
Version: | 420+ | ||
Hardware: | Mac | ||
OS: | OS X 10.4 | ||
URL: | http://www.bananarepublic.com/ | ||
Bug Depends on: | |||
Bug Blocks: | 7670 |
Description
Geoffrey Garen
2006-01-17 15:11:35 PST
This is a third party bug. I am unable to reproduce the issue any longer. I did experience the issue a few months ago myself, but it appears that http://www.bananarepublic.com will load as expected without changing the User-Agent. Using version 2.0.3 (417.8) This has been solved apparently, closing as worksforme, removing hitlist keyword. Re-adding HitList keyword. We need to be able to track HitList bugs that have been fixed. Unfortunately, the WebKit nightly builds still get the "your browser sucks" page here: http://www.bananarepublic.com/browse/info.do?cid=8808 Their browser-sniffing code could still use some work, but I'm not sure whether it's worth pursuing. It'd be nice if they did something like Yahoo's Graded Browser Support. http://developer.yahoo.net/yui/articles/gbs/gbs.html Pages like these still fail to render: http://www.bananarepublic.com/browse/product.do?cid=5349&pid=361832 http://www.bananarepublic.com/browse/product.do?cid=7051&pid=374936 (In reply to comment #6) > Pages like these still fail to render: > http://www.bananarepublic.com/browse/product.do?cid=5349&pid=361832 > http://www.bananarepublic.com/browse/product.do?cid=7051&pid=374936 > While you can sort of access the site, it still does not work correctly in Safari. Once you click on any of the clothes items it takes you to a page but it doesn't show you the item or any way to purchase it. This and bug #6623 are the same -- both mention all three related websites (Old Navy, Banana Republic, and Gap), all of which run the same backend that causes the various bugs. While it's true that these sites use the same backend, we've noticed a few bugs that show up only for some and not others. We'd also like to track support for each site separately for the sake of people who aren't familiar with the underlying issues. The original issue mentioned in this bug has been resolved, so I'm closing it. The new issues mentioned have their own bugs now. |