Browse files

Docs: Update section about the X-UA-Compatible meta option

Chrome Frame is not supported anymore and we removed the option in
This commit removes the documentation about Chrome Frame in the
X-UA-Compatible meta tag docs.

Related to #1396.
  • Loading branch information...
1 parent 5bc2a98 commit 2cf1ef7ceaf034b189b23868dd16d1908059e6fa @drublic drublic committed Aug 14, 2013
Showing with 5 additions and 9 deletions.
  1. +5 −9 doc/
14 doc/
@@ -60,21 +60,17 @@ possible that they're not using the latest rendering engine their browser
contains. To fix this, use:
-<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
+<meta http-equiv="X-UA-Compatible" content="IE=edge">
-The `meta` tag tells the IE rendering engine two things:
-1. It should use the latest, or edge, version of the IE rendering environment
-2. If already installed, it should use the Google Chrome Frame rendering
- engine.
+The `meta` tag tells the IE rendering engine it should use the latest, or edge,
+version of the IE rendering environment.
This `meta` tag ensures that anyone browsing your site in IE is treated to the
best possible user experience that their browser can offer.
-This line breaks validation, and the Google Chrome Frame part won't work inside
-a conditional comment. To avoid these edge case issues it is recommended that
-you **remove this line and use the `.htaccess`** (or other server config)
+This line breaks validation. To avoid this edge case issue it is recommended
+that you **remove this line and use the `.htaccess`** (or other server config)
to send these headers instead. You also might want to read [Validating:

0 comments on commit 2cf1ef7

Please sign in to comment.