Front-End related JS

1. Mailchimp.js: Online tool for subscribing to RSS via email

2. Ga.js:a Java script that Google has launched to count website information. Statistics and tracking information and statistical reports can be obtained from the Googleanalytics website.

3. < meta HTTP-EQUIV = "x-ua-compatible" content = "ie=edge,chrome=1"/>

Content ="ie=edge,chrome=1"Detailed

< meta HTTP-EQUIV ="x-ua-compatible"Content ="ie=edge,chrome=1"/>This is a special tag for IE8, used to specify IE8 browser to simulate the rendering of a particular version of IE (such as people annoying IE6), to solve some of the compatibility problems, such as the specific way to simulate IE7 as follows:< meta HTTP-EQUIV ="x-ua-compatible"Content ="Ie=emulateie7"/>But what makes me curious is that there is a value like chrome behind this tag, ie can also simulate chrome.?A quick search, only to understand that the original is not Microsoft enhanced IE, but Google did a plug-in: Google Chrome frame (google embedded browser framework GCF). This plugin can keep the user's IE browser intact, but when users browse the Web, they actually use the Google Chrome kernel and support IE6,7, 8, and many other versions of IE browser, Google this corner digging the real force!The meta tag mentioned above is used to specify that the page is rendered using the chrome kernel after the GCF is installed. Gcf:http://code.google.com/intl/zh-cn/chrome/chromeframe/After the installation is complete, if you want to render a page using GCF, just precede the address of the page with GCF: Yes, for example: gcf:http://cooleep.comBut what if you want to specify the page default to use GCF for rendering at development time, and if the GCF is not installed and then rendered using the IE kernel?is to use this tag. Tag usage: Read the development document under Chrome (http://www.chromium.org/developers/how-tos/chrome-frame-getting-started, need to turn-wall), below to briefly explain the syntax of this tag. 1most basic usage: add to the head of the page1< meta HTTP-EQUIV ="x-ua-compatible"Content ="chrome=1">to declare that the current page is rendered with the chrome kernel. What's more complicated is the usage that I saw at the beginning of this article:1< meta HTTP-EQUIV ="x-ua-compatible"Content ="ie=edge,chrome=1"/>the effect of this writing is that if the GCF is installed, a GCF is used to render the page, and if the GCF is installed, the highest version of the IE kernel is used for rendering. 2To enable the specified page to render using the GCF kernel by modifying the HTTP header file: Include the following information in the HTTP header file: X-ua-compatible:chrome=1In the Apache server, make sure that the mod_headers and mod_setenvif files are available, and then add the following configuration information to the httpd.conf:< Ifmodule mod_setenvif.c>< Ifmodule mod_headers.c>browsermatch chromeframe gcfheader append X-ua-compatible"chrome=1"env=GCF on IIS7 or later servers, just modify the Web. config file and add the following information:< configuration >< system.webserver >< httpprotocol >< customheaders >< Add name ="x-ua-compatible"Value ="chrome=1"/></customheaders >
Front-End related JS