[cosmo-dev] Safari 2

[Mikeal Rogers]

WebKit != Safari

The way buttons, drop downs, and test fields are drawn get pulled from  
the system level UI libraries. The networking libraries are all shared  
system libraries as well.

The issues I've encountered just running this .app for 10 minutes are  
far above issues i normally run in to using a VM, namely crashes and  
extremely slow load times.

This isn't a reasonable solution for QA to regress bugs against.

-Mikeal

On Nov 13, 2007, at November 13, 200712:55 PM, Bobby Rullo wrote:

> Mikeal,
>
> It replaces WebKit by bundling it inside of the application, so you  
> are using the WebKit that came with that version of Safari.
>
> bobby
>
>
>
> On Nov 13, 2007, at 12:13 PM, Mikeal Rogers wrote:
>
>>
>> On Nov 13, 2007, at November 13, 200711:41 AM, Bobby Rullo wrote:
>>
>>> http://michelf.com/projects/multi-safari/
>>
>> This doesn't replace the system level shared libraries, which make  
>> up a decent amount of Safari unless I'm mistaken.
>>
>> This solution is actually worse than a VM. If you find a bug you  
>> can't really be sure enough that it's a real problem until you  
>> check it out on a full Tiger install. You can't regress a bug with  
>> it because you're not really running 100% Safari 2.
>>
>> You can't create a Tiger VM, I tried.
>>
>> Unless we dedicate extra hardware we can't really support this.
>>
>> -Mikeal
>> _______________________________________________
>> 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

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.osafoundation.org/pipermail/cosmo-dev/attachments/20071113/16d14e73/attachment.html