Chrome: Compatibility of Google in the browser war

In September 2, Google officially released its open-source browser chrome beta version for download.

As a developer, in addition to the fresh feeling and new experience that Google browser brings to us, they may unconsciously think about compatibility with other browsers, after all, we have been overwhelmed by IE6, IE7, and Firefox. This is not just the IE8 release of beta2. Now Chrome is coming again. We can't help but ask: chrome, will you do it?

Google Chrome draws on some technologies derived from Apple WebKit and Mozilla Firefox. In this regard, Chrome is closer to ff. After a simple trial, we found that Google, Baidu, Sina, Douban, and fresh fruit are well compatible. In addition, it is particularly worth mentioning that the page loading speed of Chrome is very fast, and it is not known whether the design structure of the independent process is used.

Despite this, chrome shows its uniqueness for some page elements. For example, the menu object of ASP. NET is displayed in <Table> mode regardless of IE or Firefox, for example:

Code
< Table ID = "Ctl00_navmenu" Class = "Ctl00_navmenu_2" Cellpadding = "0" Cellspacing = "0" Border = "0" >
< Tr >
< TD Onmouseover = "Menu_hoverstatic (this )" Onmouseout = "Menu_unhover (this )" Onkeyup = "Menu_key (this )" ID = "Ctl00_navmenun0" > < Table Cellpadding = "0" Cellspacing = "0" Border = "0" Width = "100%" >
< Tr >
< TD Style = "White-space: nowrap ;" > < A Class = "Ctl00_navmenu_1" Href = "Menu1.aspx" > Menu item 1 </ A > </ TD >
</ Tr >
</ Table > </ TD > < TD Style = "Width: 3px ;" > </ TD > < TD Onmouseover = "Menu_hoverstatic (this )" Onmouseout = "Menu_unhover (this )" Onkeyup = "Menu_key (this )" ID = "Ctl00_navmenun1" > < Table Cellpadding = "0" Cellspacing = "0" Border = "0" Width = "100%" >
< Tr >
< TD Style = "White-space: nowrap ;" > < A Class = "Ctl00_navmenu_1" Href = "Menu2.aspx" > Menu item 2 </ A > </ TD >
</ Tr >
</ Table > </ TD > < TD Style = "Width: 3px ;" > </ TD > < TD Onmouseover = "Menu_hoverstatic (this )" Onmouseout = "Menu_unhover (this )" Onkeyup = "Menu_key (this )" ID = "Ctl00_navmenun2" > < Table Class = "Selected ctl00_navmenu_4" Cellpadding = "0" Cellspacing = "0" Border = "0" Width = "100%" >
< Tr >
< TD Style = "White-space: nowrap ;" > < A Class = "Ctl00_navmenu_1 selected ctl00_navmenu_3" Href = "Menu3.aspx" Style = "Border-style: none; font-size: 1em ;" > Menu item 3 </ A > </ TD >
</ Tr >
</ Table > </ TD >
</ Tr >
</ Table >

 

However, Chrome is different. Chrome uses another rendering method, which should be specially processed by Chrome, as shown below:

 

Code
< Div ID = "Ctl00_navmenu" >  
< Span > < A Class = "Ctl00_navmenu_1" Href = "Menu1.aspx" > Menu item 1 </ A > </ Span >
< Span > < A Class = "Ctl00_navmenu_1" Href = "Menu2.aspx" > Menu item 2 </ A > </ Span >
< Span > < A Class = "Ctl00_navmenu_1" Href = "Menu3.aspx" > Menu item 3 </ A > </ Span >  
</ Div >

 

Chrome replaces the outer <Table> with <div>, and uses <span> to replace the nested <Table>. After processingCodeIt is greatly streamlined and more in line with the current Web Design Trend of Div + CSS.

In any case, Google Chrome brings us a completely different experience from the past, and is only a beta version. We believe that with the continuous improvement of the Google team, google Chrome can bring us more surprises.

 

Update:

Seeing that my friends mentioned Apple's Safari in their replies, I quickly downloaded the latest Windows version from the apple website, tested the same code, and found that safari has the same rendering code as chrome, is it because chrome uses Apple WebKit?

 

Someone in the ASP. NET Forum replied:

Safari and ie5.0 are considered downlevel browsers by ASP. NET. By default you won't get rich renderings for either of those.

ASP. NET regards safari and ie5.0 as low-level browsers. By default, these two browsers cannot be used for rich content presentation.

 

If this is related to Chrome's use of Apple WebKit, you can explain it. Unlike the presentation of IE and FF, the Chrome browser is related to ASP. NET. ASP. NET considers chrome as a low-level browser and returns simple code, rather than the browser's own special processing.

 

Update2:

What is downlevel browsers? Lower-layer Browser
Early browsers with basic features and functions. Browsers that do not support script editing, dynamic HTML (DHTML), DHTML behavior, or Extensible Markup Language (XML) are generally considered as lower-layer browsers.