Bug 7628 - Gap.com, banannarepublic.com, oldnavy.com say Safari 417.9 won't work
Summary: Gap.com, banannarepublic.com, oldnavy.com say Safari 417.9 won't work
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks: 7670 7671
  Show dependency tree / graph
 
Reported: 2006-03-06 12:01 PST by Geoffrey Garen
Modified: 2006-04-10 14:11 PDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Geoffrey Garen 2006-03-06 12:01:54 PST 
This bug is also in Radar as <rdar://4464698>

* SUMMARY
Safari 2.0.3 (417.9): www.gap.com doesn't support Safari even though it says it does

* STEPS TO REPRODUCE
1. Launch Safari 417.9
2. Go to www.gap.com

* RESULTS
We're sorry but we do not support the version of the browser you are using. Our site works best with the following browsers:

Netscape 7
Mozilla (including Firefox)
Safari 2.0.3 and above (Safari 2.0.3 is part of the Mac OS X v10.4.4 update)

See image.

* REGRESSION
Occurs:
Safari 2.0.3 (417.9)
Safari 2.0.3 (417.9)

Doesn't occur:
Safari 2.0.3 (417.8)

<GMT02-Mar-2006 20:30:05GMT> Leslie Case:
Doesn't occur with www.gapinc.com, but does occur with all their brands.

<GMT02-Mar-2006 22:55:23GMT> Alice Liu:
problem seen:
(417.9)
Safari TOT (420+)

problem not seen:
(417.8)
Leopard (521.7.2)

I talked to Tim Hatcher about this and he thinks that Gap is probably doing their Safari version check too strictly or incorrectly, and that it's not a regression on the Safari side.  This made sense until I tested Leopard and it worked.

<GMT03-Mar-2006 23:22:04GMT> Alice Liu:
this might end up being an evangelism issue, but we should see what we can figure out on our end first.
Comment 1 Geoffrey Garen 2006-03-06 14:09:33 PST 
gap.com's sniffing code compares for ">= 417.7". When we bumped the WebKit version number from 417.9 to 417.10, it became numerically less than 417.7.

We can fix this temporarily by bumping the WebKit version number to 418, but we'll need to get in touch with them about fixing it on their end as well.
Comment 2 David Kilzer (:ddkilzer) 2006-03-06 19:43:29 PST 
Nightly builds don't work on their site, either.  Their browser sniffing code needs more work.  Isn't this a duplicate of Bug 6623?
Comment 3 Geoffrey Garen 2006-03-07 09:40:03 PST 
Not a dup because bug 6623 tracks failure to render.
Comment 4 Brian Hagan 2006-04-03 11:26:43 PDT 
This should have been fixed as of 3/28. Can someone please hit one of the three sites with a nightly build?
Comment 5 Alice Liu 2006-04-10 14:06:39 PDT 
working on 10.4.6 (417.9.2) but not TOT (420+).
Comment 6 Geoffrey Garen 2006-04-10 14:11:27 PDT 
The sites still fail to parse "420+", which is the version number of our latest sources, but they work with 417.9. Since we don't use "+" in released versions of Safari, I think we can close this bug. But it would be nice if the sites' parsing improved to include "420+" as well.