Christopher R wrote:
> I've been using Opera for a long time and I think it is a good 
> browser but I will be making a switch over to chrome.

For browsing, OK - doesn't really matter which browser one uses as long
as it isn't too old.

For web development it is a little different, but we all have our
preferences. I develop in/for Opera, and make sure all others are
rendering fine.

> I have more of a statement to make about Chrome when I tried the beta
>  version (I know it's still lingers to some extent as a beta) did it 
> seem to anyone that it appears to render pages almost identical to IE
> ?

That Chrome render almost identical to IE should not come as a surprise.
For the average web page almost all relatively new browser versions
render the same. That's the result of having web standards, and that
pages are made to "appear the same" everywhere.
Browser developers are more and more onto the same route regarding CSS
standards, and all fixes we web developers use for old IE makes even
that browser appear to render most pages the same as all others.
(Some web developers do of course do this in reverse - build for IE and
fix others, but the result is in most cases the same.)

When challenged the various engines reveal differences, but apart from
bugs and lack of support for certain CSS parts the result on screens is
pretty much the same - for the reasons mentioned above.


Chrome uses the WebKit rendering engine, *and* identifies itself as
WebKit when probed for CSS based rendering.


That a browser is built on a specific rendering engine doesn't mean its
CSS rendering is identical to other browsers using the same engine, down
to the minutest details. Engine versions differ, and branching/forking
counts for some differences since not all development is ported - or is
really portable - back to the main engine and out to the other branches.

Example: WebKit was forked off of the KHTML engine, but modifications to
the WebKit engine has only to a small degree been ported back to the
KHTML engine. (The WebKit engine still responds to a few KHTML specific
CSS selectors, although most are replaced by specific WebKit selectors
by now.)

Browser developers historically don't cooperate well enough to help each
other keep the various engine versions coherent. Lots of competition out
there, and various browser developers are generally more interested in
presenting and promoting each browser's uniqueness than its relationship
to other browsers, to the regular web surfer.


A list over browsers vs. rendering engines is found here...
<http://www.gunlaug.no/contents/wd_additions_40.html>
...and if in doubt you can use the "CSS Sledgehammer" probing - the
image above that list - to see which CSS rendering engine/engine-version
any browser has or uses. Around 99.9% accuracy for browsers in regular
use can be expected for the probing-method I use :-)

(One can't easily probe the latest Opera versions btw, but that's no
problem as long as one can probe all others.)

regards
        Georg
-- 
http://www.gunlaug.no
______________________________________________________________________
css-discuss [[email protected]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
List policies -- http://css-discuss.org/policies.html
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/

Reply via email to