To my eyes, the reason is that the font itself is larger on the right
hand side. Naturally this will give a larger line-height, unless you
have specified otherwise.
Regards,
Mike
Mike Brockington
Web Development Specialist
www.calcResult.com
www.stephanieBlakey.me.uk
www.edinburgh.gov.uk
This
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
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
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
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
Any script that relies on an array being ordered, without actually doing
a sort() is seriously deficient. As you mentioned yourself, this
behaviour is entirely in agreement with the JS spec.
Regards,
Mike
From: li...@webstandardsgroup.org
I said indeed serious problem, although that is indeed debatable.
for in should indeed be used carefully, it's not quite reliable and browsera
all have different behaviours, although chrome's behaviour is the most
unreliable (if we can call it like that) due to the order of elements
returned.
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 this is a
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
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
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 different font rendering.
Safari's fonts are way smaller, hence my
11 matches
Mail list logo
