[Ham-Mac] Safari glitches

[Mark Cohen]

So, I think the issue is that Safari doesn't support XSL/XSLT in the  
proper ways which causes lots of sites to break with it, for example  
Safari doesn't follow includes in client-side XSLT. Safari tends to  
just die w/o any error, broken line number or anything..

This is IMHO endemic to the way that Apple tends to code most of their  
stuff.

It's great to say "We support ### of Macs in house all using Safari  
and don't see any problems" But if QA worked like that, we would never  
have stable code. Just because it works for one person, doesn't mean  
that it doesn't have problems that need to be solved.

Safari is MUCH faster than Firefox, but sometimes you would rather  
drive a stable VW and reliably go 65, then drive a Ferrari that was  
made with plastic lug nuts and go 165. :)

-Mark
K6EF

On Jan 24, 2008, at 11:21 AM, grand-pa wrote:

> Hi
> I have had no problems with safari 3 in new tower + Leopard
> for interesting info on browsers goto  :
> http://www.news.com/Acid2,-Acid3,-and-the-power-of-default/2010-1013_3-6227171.html?tag=html.alert.hed
>
>
> seems like IE_7 and IE_8 are some of the few browsers that follow  
> this standard
> Safari was mentioned along with Firefox as being compliant with the  
> ACID Test_2 and possibly ACID test_3 forthcoming
> interesting article
>
> 73
> WB8UGI
>
> larryhoover at mac.com
> http://web.mac.com/larryhoover
>
> Home#  313-537-5257
> Cell#     313-530-2484
> -------------------------------------------
> "Love is what's in the room with you at Christmas
> if you stop opening presents and listen."
>
>
> _______________________________________________
> Ham-Mac mailing list
> Ham-Mac at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/ham-mac