Re: [css-d] Copy and Paste: about the Chrome browser

[Bobby Jack]

--- On Fri, 9/5/08, Gabriele Romanato [EMAIL PROTECTED] wrote:

 during my long experience in CSS testing, I've learned
 a great lesson about web browsers. There are two types of
 browsers: original browsers and clonings.
 ...
 [lots more]

Gabriele,

This is dangerously close to being off-topic, but I'm sure the old-timers can 
judge this far better than I can! :) So, I'll bite.

Your tone and choice of words (clonings, copied and pasted) seems quite 
negative - would you prefer to have new incompatibilities to deal with, or 
innovation in other areas of the browser, such as UI and feature improvements?

Sharing of rendering engines is perfectly legitimate, in my book, and gives us 
web developers/designers further options as to how we test. For example, the 
environment I'm currently working in does not allow me to install Safari, 
making testing on that browser (and, thus, WebKit) something of a challenge. 
Chrome, however, DOES install, so greater numbers of 'clones' lead to a more 
favourable situation for cross-browser compatibility.

I agree that, from a what's implemented, and what do I need to hack 
perspective, Chrome isn't very exciting, and we barely need to discuss it from 
a CSS point of view, but that doesn't mean 'clones' should not exist, and it 
doesn't make them any less useful.

- Bobby



  
__
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/

Re: [css-d] Copy and Paste: about the Chrome browser

[Ryan Doherty]

On Sep 4, 2008, at 11:15 PM, Gabriele Romanato wrote:
 Original browsers have their own rendering engine which is unique and
 different from any other
 browser (Firefox, IE, Safari, Opera),

Firefox and Safari use open-source rendering engines, available for  
anyone to use. Opera and IE's rendering engines are unique in that  
they are closed source and only available to them.


 while clonings have simply copied and
 pasted their rendering
 engine from original browsers ones (K-Meleon, Flock, ecc.)

They didn't 'copy and paste' their rendering engines. They did the  
exact same thing Firefox, Safari, Camino and Chrome did: they put an  
open-source rendering engine in their browser.

Right now I wouldn't do any serious testing in Chrome as it's beta and  
they are a few months behind on their Webkit version. But if it gains  
marketshare and they add new CSS features to it and don't push it back  
to Webkit, we will probably have to test it too.

Don't be so quick to discount a new browser. It's great to have more  
options for users and more competition :)

-Ryan

Ryan Doherty
[EMAIL PROTECTED]

__
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/