Re: [css-wywiwyg] browser interpretation of css

I suggest you look at some of the open source browser engines (Gecko, WebKit). You'll discover their immense complexity (millions of lines of code), piles of historical artifact, and different levels of implementation for old and new CSS features.

Your question is akin to "Why aren't all translations of the Bible into language X exactly the same". There are many reasons, both deep and shallow, why they are not.

Simon

On May 7, 2012, at 4:13 PM, Rik Schaaf wrote:

> I don't think he meant the browsers themselves, but the content they display. 
> For instance: If one says width: 80px, all browsers should handle it the same way (with/without border / padding / margin) 
> 
> This example is handled the same way by at least the major browsers, but other properties that have minor undefined things will show differently sometimes.
> 
> On 8 mei 2012, at 00:26, "Brian Manthos" <brianman@microsoft.com> wrote:
> 
>>> I think we all already dreamt of a perfect web development world, in which all browsers are behaving the same.
>> 
>> I would call this a horrible stagnant world, not a perfect one.
>> 
>> 
>> Option A
>> If you want all browsers to behave the same, rewind to V1 of the first web browser and halt all innovation from there forward.  I think we'd all hate that instance if it were forced on us in 2012.
>> 
>> Option B
>> Pick 1 vendor today and scrap all rest.  Now you have a monopoly where all web browsers are behaving the same.  Seems like there's no financial incentive to innovate or invest in making that browser better.  Becomes option A with a little more advancement.
>> 
>> Option C
>> Pick 2 vendors and have them collaborate heavily and merge.  Repeat until you've produced option B.
>> 
>> 
>> Did you have another option in mind?
>> 
>> 
>> 
>

Received on Tuesday, 8 May 2012 00:24:38 UTC