RE: [WSG] Chrome and Safari render the same...or do they?

2009-01-09 Thread michael.brockington
This message does not reflect the opinions of any entity other than the author alone. From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Jens-Uwe Korff Sent: 09 January 2009 05:22 To: wsg@webstandardsgroup.org Subject: RE: [WSG] Chrome

Re: [WSG] Chrome and Safari render the same...or do they?

2009-01-08 Thread Gunlaug Sørtun
Jens-Uwe Korff wrote: I'm running into big rendering differences between Google Chrome and Safari 3.1/PC. They are said to render pages the same, given that they're using the same Webkit engine. They're using the WebKit engine, not necessarily the same version. Safari is at version 3.2.1 last

Re: [WSG] Chrome and Safari render the same...or do they?

2009-01-08 Thread Simon Pascal Klein
I think this comes down more to which font rasterisation engine a system is using. I don’t think Safari on Windows for example has full access to AAT and Quartz and thus will render type using ClearType and GDI on Windows. Add Firefox into the mix which uses Cairo and you’ll get different

Re: [WSG] Chrome and Safari render the same...or do they?

2009-01-08 Thread Johan Douma
Hi everybody, Even though Chrome is based on Webkit, Chrome actually uses another graphics/rendering engine (the drawing layer) called Skia (source code: http://src.chromium.org/viewvc/chrome/trunk/src/skia/). A bit like the javascript engines, Google didn't use webkits' javascript engine

Re: [WSG] Chrome and Safari render the same...or do they?

2009-01-08 Thread Johan Douma
Just though I'd let you know about this, I actually think this is a pretty serious problem, because it breaks a lot of scripts and doesn't conform with the other browsers even though it conforms to the javascript spec. V8 (chrome's js engine) can take the values in an array in a random order. If

RE: [WSG] Chrome and Safari render the same...or do they?

2009-01-08 Thread michael.brockington
...@webstandardsgroup.org] On Behalf Of Johan Douma Sent: 08 January 2009 11:22 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Chrome and Safari render the same...or do they? Just though I'd let you know about this, I actually think this is a pretty serious problem, because it breaks a lot of scripts

Re: [WSG] Chrome and Safari render the same...or do they?

2009-01-08 Thread Johan Douma
-- *From:* li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] *On Behalf Of *Johan Douma *Sent:* 08 January 2009 11:22 *To:* wsg@webstandardsgroup.org *Subject:* Re: [WSG] Chrome and Safari render the same...or do they? Just though I'd let you know about this, I actually

Re: [WSG] Chrome and Safari render the same...or do they?

2009-01-08 Thread Christian Montoya
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org] On Behalf Of Johan Douma Sent: 08 January 2009 11:22 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Chrome and Safari render the same...or do they? Just though I'd let you know about this, I actually think

Re: [WSG] Chrome and Safari render the same...or do they?

2009-01-08 Thread David Hucklesby
On Thu, 8 Jan 2009 16:36:45 +1100, Jens-Uwe Korff wrote: Hi experts, I'm running into big rendering differences between Google Chrome and Safari 3.1/PC. They are said to render pages the same, given that they're using the same Webkit engine. The differences seem to be mainly due to the

RE: [WSG] Chrome and Safari render the same...or do they?

2009-01-08 Thread Jens-Uwe Korff
Hi all, thanks for your suggestions. I'm attaching a side-by-side comparison of a snippet of the page since I cannot put any code live, hoping the attachment gets delivered. Safari is on the left, Chrome on the right. If you cannot see the attachment, it shows how the graphical background

Re: [WSG] Chrome and Safari

2008-10-16 Thread Ben Buchanan
Seeing as though Google's new Chrome browser uses the same rendering engine as Apple's Safari, would it be acceptable to test browser layout issues in Chrome and assume the same CSS solutions apply in Safari? Does anyone know of any distinct differences in CSS rendering between the 2 browsers?

Re: [WSG] Chrome and Safari

2008-10-16 Thread Johan Douma
Not only JS, there are differences in CSS as well. Shadows appear, but kinda buggy, not as it should. text-shadow and box-shadow. The rounded borders are not antialiased (as in aliased or pixelated) in Chrome whereas FF3 and Safari handle it correctly. And font-face doesn't work at all, whereas

Re: [WSG] Chrome and Safari

2008-10-16 Thread David Hucklesby
On Thu, 16 Oct 2008 10:49:59 +1000, [EMAIL PROTECTED] wrote: Hi, Seeing as though Google's new Chrome browser uses the same rendering engine as Apple's Safari, would it be acceptable to test browser layout issues in Chrome and assume the same CSS solutions apply in Safari? Does anyone

RE: [WSG] Chrome and Safari

2008-10-15 Thread Damian Edwards
From what I can tell Safari 3.1 for Windows and Google Chrome use exactly the same version of WebKit (according to their respective user agents anyway), so they should render identically. JavaScript DOM support is a different matter though. Regards, Damian Edwards Microsoft MVP | ASP/ASP.NET

Re: [WSG] Chrome and Safari

2008-10-15 Thread Brett Patterson
May I ask how so, for future reference please? On Wed, Oct 15, 2008 at 8:59 PM, Damian Edwards [EMAIL PROTECTED]wrote: From what I can tell Safari 3.1 for Windows and Google Chrome use exactly the same version of WebKit (according to their respective user agents anyway), so they should render

RE: [WSG] Chrome and Safari

2008-10-15 Thread Damian Edwards
://www.readify.net/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Brett Patterson Sent: Thursday, 16 October 2008 12:06 To: wsg@webstandardsgroup.org Subject: Re: [WSG] Chrome and Safari May I ask how so, for future reference please? On Wed, Oct 15, 2008 at 8:59 PM, Damian Edwards

Re: [WSG] Chrome and Safari

2008-10-15 Thread Jon Warner
Not from what I've seen - safari (pc based) can be fine, chrome not. I'd have to go through my history somewhat to link theese pages/sites but if you must have the proof... At the end of the day never assume 'just cos one works another similar will'. Chrome may be based on something, doesn;t