[cosmo-dev] Safari 2

[Jeremy Epstein]

-1 to dropping safari 2.0--

Safari 2 is stable and capable enough to be the "IE-6 of mac browsers".
Also (at least for me) it doesn't/didn't automatically upgrade to 3.0  
(I'm not on leopard) and have no immediate plans to upgrade my OS.

I would hold off eliminating support until safari 2.0 drops below 40%  
of the active installed base.

YOu guys are not developing enterprise software where you can request  
specific versions (to an extent). furthermore, if "compatible with  
safari 2" means "compatible with safari 3"  I'd stick with it for as  
long as possible.





On Nov 13, 2007, at 11:41 AM, Bobby Rullo wrote:

> -0 to dropping Safari 2.0 right now.
> +1 to waiting a bit (like a couple of months)
>
> I don't think it's a great idea to drop support of an OS's default  
> browser mere weeks after the new version has been released.   
> Believe me, I hate Safari 2 quirks as much as anyone else, but I  
> don't want to turn anyone off from Hub adoption.
>
> There is a way to test multiple versions of Safari in one OS X -  
> check out:
>
> http://michelf.com/projects/multi-safari/
>
> Bobby
>
> On Nov 12, 2007, at 10:14 PM, Aparna Kadakia wrote:
>
>> +1 for going with option #1
>> Getting Hub statistics might help make a case for it.
>>
>> On Nov 12, 2007, at 7:02 PM, Matthew Eernisse wrote:
>>
>>> I think we should seriously consider option 1 -- discontinuing  
>>> support for  Safari 2. To validate this idea, would it be  
>>> possible to find out the number of Hub users are actually still  
>>> using it?
>>>
>>> Whatever we do, I think we should only be supporting one version  
>>> at a time.
>>>
>>> If we do go that route, it's worth noting that I'm in the  
>>> opposite boat -- my creaky old G4 will not run Leopard. I would  
>>> need something to run it on.
>>>
>>>
>>> Matthew
>>>
>>>
>>> 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