[cosmo-dev] Safari 2

[Bobby Rullo]

+1 IFF we have a page for "unsupported browsers" - like "Your browser  
is not supported by Chandler Server. Please use one of the following..."

Most sites accomplish this via a whitelist - only allow known  
supported browsers. I am against that in principle - it basically says  
"only browsers which we know can play along" and it means that if some  
new cool browser/platform is introduced which completely supports web- 
standards we would be blocking them just because we didn't know about  
them.

For this reason I'd rather have a blacklist - block versions web  
browsers of the major families (Firefox, Safari, IE) which are known  
to break.

bobby

On Nov 14, 2007, at 3:03 PM, Matthew Eernisse wrote:

> +1
>
> 1. It's a tiny slice of our user population
> 2. It's being rolled out in Software Update
> 3. It's not a browser that IT departments are likely to have  
> standardized on (a la IE6)
> 4. Apple users tend to upgrade quickly
> 5. It will suck way less than Safari 2, so the dev/testing load  
> should be lower
>
> Travis Vachon wrote:
>> +1
>> On Nov 14, 2007, at 2:00 PM, Mikeal Rogers wrote:
>>> I don't think this adds confusion, I think it basically solves our  
>>> dilemma.
>>>
>>> We've always supported the "latest" Safari 2 as updated through  
>>> the operating system. If Tiger users have a Safari upgrade path  
>>> it's only a matter of time before the vast majority are using  
>>> Safari 3.
>>>
>>> +1 to cutting Safari 2 for Safari 3.
>>>
>>> -Mikeal
>>>
>>> On Nov 14, 2007, at November 14, 20071:56 PM, Ted Leung wrote:
>>>
>>>> Not to add any more confusion, but as of 10.4.11, Safari 3 is the  
>>>> default on Tiger, as well...
>>>>
>>>> <http://docs.info.apple.com/article.html?artnum=306297>
>>>>
>>>> Ted
>>>>
>>>> On Nov 12, 2007, at 5:21 PM, Travis Vachon wrote:
>>>>
>>>>> Hi folks
>>>>>
>>>>> With the release of Leopard many of us (developers and qa) are  
>>>>> currently unable to test Safari 2. I'm not totally sure what the  
>>>>> best solution to this is. Ideally we could install Safari 2  
>>>>> alongside 3 and continue testing happily, but so far the search  
>>>>> for easy ways to do this has been fruitless.
>>>>>
>>>>> I'd like to use this thread to consider a number of possible  
>>>>> ways we can handle this. Off the top of my head:
>>>>>
>>>>> 1) Discontinue support for Safari 2.
>>>>> 2) Provide a semi-public instance of Tiger for testing and set  
>>>>> appropriate parties up with access.
>>>>> 3) Invest some cycles figuring out a way to run both Safari 2  
>>>>> and 3 on Leopard.
>>>>> 4) ??
>>>>>
>>>>>
>>>>> For what it's worth I think we should seriously consider 1) in  
>>>>> the next few months. In my mind Safari's browser share doesn't  
>>>>> justify supporting old versions in the same way we support IE 6.  
>>>>> That said, if a Tiger release of Safari 3 is in the works it  
>>>>> might be good to wait for that.
>>>>>
>>>>> In the mean time I'm not sure which of 2 or 3 I find more  
>>>>> appealing. Both seem like a non-trivial amount of pain, but 3  
>>>>> seems like a potential goose chase.
>>>>>
>>>>> Thoughts?
>>>>>
>>>>> -Travis
>>>>> _______________________________________________
>>>>> cosmo-dev mailing list
>>>>> cosmo-dev at lists.osafoundation.org
>>>>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>>>>
>>>> _______________________________________________
>>>> cosmo-dev mailing list
>>>> cosmo-dev at lists.osafoundation.org
>>>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>>>
>>> _______________________________________________
>>> cosmo-dev mailing list
>>> cosmo-dev at lists.osafoundation.org
>>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>> _______________________________________________
>> cosmo-dev mailing list
>> cosmo-dev at lists.osafoundation.org
>> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev
>
> _______________________________________________
> cosmo-dev mailing list
> cosmo-dev at lists.osafoundation.org
> http://lists.osafoundation.org/mailman/listinfo/cosmo-dev