Enable the webpage to automatically call the speed mode (& lt; meta name = & quot; renderer & quot; content = & quot; webkit & quot; & gt;) of the dual-core browser, rendererwebkit

Allows the webpage to automatically call the speed mode of the dual-core browser (<meta name = "renderer" content = "webkit">), rendererwebkit

Background: I recently launched a website. After the leaflet server was opened, it was garbled every time. No, it was clearly formatted locally. Then I found that, 360 is opened in "compatible mode". This is embarrassing. When a user opens it, It is garbled. how bad the user experience is! No matter what mode you are. After some research, I finally found a solution.

Most mainstream browsers in China are dual-core browsers: they are used for high-speed browsing of common websites based on the Webkit kernel. The IE-based kernel is used for compatibility with online banking and old websites. Taking several browsers of 360 as an example, we first use the Webkit kernel to render mainstream websites. Only a small number of websites are rendered through the IE kernel to ensure page compatibility. When we add the kernel control Meta tag whose property value is renderer on the page, it will tell the browser which kernel should be used for rendering the URL and the browser will read this tag, switch the corresponding kernel immediately. And apply this behavior to all the URLs under this second-level domain name. The Code is as follows:

Among them, there are three content values, which are the nature of each kernel:

 

 
  
 
   
 
    
Content value
 
    
Webkit
 
    
Ie-stand
 
    
Ie-comp
 
   
 
   
 
    
Mode
 
    
High speed mode
 
    
Standard IE Mode
 
    
IE compatibility mode
 
   
 
   
 
    
HTML5 supported?
 
    
 
    
 
    
Bytes
 
   
 
   
 
    
ActiveX Control supported?
 
    
Bytes
 
    
 
    
 
   
 
   
 
    
Compatibility
 
    
Chrome 21
 
    
IE9/IE10/IE11 (depending on your IE)
 
    
IE6/IE7