removed IE6 and IE7 mentions

Author: coliff

new_feature.js

@@ -51,6 +51,7 @@ var feature = {
   name: promptValue('Feature Name'),
   status: promptValue('Status', ['use', 'avoid', 'caution']),
   tags: promptValue('Tags', ['gtie6', 'gtie7', 'gtie8', 'prefixes', 'polyfill', 'fallback', 'none'], true),
+  tags: promptValue('Tags', ['gtie7', 'gtie8', 'prefixes', 'polyfill', 'fallback', 'none'], true),
   kind: promptValue('Type', ['css', 'html', 'js', 'api', 'svg'])
 };
 

posts/css-fixed.md

@@ -4,6 +4,6 @@ tags: none
 kind: css
 polyfillurls:
 
-Fixed positioning isn't supported in IE6, but is fine in IE7 and everywhere else ([except mobile, which is described at length here](http://bradfrostweb.com/blog/mobile/fixed-position/)). 
+Fixed positioning is supported in all browsers ([except mobile, which is described at length here](http://bradfrostweb.com/blog/mobile/fixed-position/)). 
 
 Use fixed positioning all you like, but you may want to check its behavior in mobile browsers afterward. There is a [messy feature detect](https://github.com/Modernizr/Modernizr/issues/167#issuecomment-2155861) if you'd like it.

posts/mediaqueries.md

@@ -4,6 +4,6 @@ tags: gtie8
 kind: css
 polyfillurls:
 
-Media Queries (MQ) work on all modern browsers. OldIE (IE6,7,8) unfortunately do not understand media queries on features, which means none of your CSS within media queries will be parsed by them. We recommend you make peace with that, but if you absolutely cannot, then you can use [Respond.js](https://github.com/scottjehl/Respond) but be aware it has performance overhead that slows down page load.
+Media Queries (MQ) work on all modern browsers. IE 8 unfortunately does not understand media queries on features, which means none of your CSS within media queries will be parsed by them. We recommend you make peace with that, but if you absolutely cannot, then you can use [Respond.js](https://github.com/scottjehl/Respond) but be aware it has performance overhead that slows down page load.
 
-If you choose a [mobile first approach](http://bradfrostweb.com/blog/web/mobile-first-responsive-web-design/), you'll be targeting smallest screens first, then the different media queries will take effect as the window/device size increases. But if the browser doesn't support media queries and you don't use a polyfill, then the 'mobile first' styles will be applied to OldIE. You can serve a [separate stylesheet for IE to help with this](http://nicolasgallagher.com/mobile-first-css-sass-and-ie/).
+If you choose a [mobile first approach](http://bradfrostweb.com/blog/web/mobile-first-responsive-web-design/), you'll be targeting smallest screens first, then the different media queries will take effect as the window/device size increases. But if the browser doesn't support media queries and you don't use a polyfill, then the 'mobile first' styles will be applied to IE 8. You can serve a [separate stylesheet for IE to help with this](http://nicolasgallagher.com/mobile-first-css-sass-and-ie/).

posts/microdata-domapi.md

@@ -1,6 +1,6 @@
 feature: Microdata DOM API
 status: use
-tags: polyfill ie6 gtie6
+tags: polyfill
 kind: API
 polyfillurls: [microdata shim](https://github.com/termi/Microdata-JS)
 moreurl: https://dev.opera.com/articles/microdata-and-the-microdata-dom-api/
@@ -10,5 +10,3 @@ Microdata is a new lightweight semantic meta-syntax. Using attributes, we can de
 The Microdata DOM API is helpful because you can manipulate items and properties on a page programmatically, perhaps to present the information in a searchable/filterable manner, or deliver it to another application somewhere else.
 
 It's supported by Firefox 16+, and pre-Blink versions of Opera.
-
-IE6+ support can be done using [this ES5/DOM shim](https://github.com/termi/ES5-DOM-SHIM)

posts/minmaxwh.md

@@ -1,9 +1,9 @@
 feature: min/max-width/height
 status: use
-tags: gtie6
+tags:
 kind: css
 polyfillurls:
 
-`min-width`, `max-height`, etc are supported everywhere as of IE7. The [min-height fast hack](http://www.dustindiaz.com/min-height-fast-hack/) has long been a reliable way of implementing min-height, but as many have sunsetted IE6 support, you likely don't need to worry about fallback anymore.
+`min-width`, `max-height`, etc are supported everywhere as of IE7.
 
 Use all you like without fallback; certainly do not use CSS expressions to mimic this behavior.

posts/opacity.md

@@ -4,4 +4,4 @@ tags: gtie8
 kind: css
 polyfillurls:
 
-CSS3 opacity allows you to modify the opacity of HTML elements. It is safe to use. For IE6-IE8, use the proprietary "filter" property to achieve the same effect.
+CSS3 opacity allows you to modify the opacity of HTML elements. It is safe to use. For IE8, use the proprietary "filter" property to achieve the same effect.

posts/selectors.md

@@ -1,48 +1,20 @@
 feature: selectors
 status: use
-tags: fallback gtie6
+tags: fallback
 kind: css
 polyfillurls:
+moreurl: https://docs.microsoft.com/en-us/previous-versions//cc351024(v=vs.85)#selectors
 
-Most CSS Selectors are supported from IE7 onwards, so you should be safe to use them. But do note that, on browsers that do not support these selectors, a whole rule will be detected as invalid if these unsupported selectors are present. For example, in IE6 `#main, p:first-child {}` would be invalid because it is unable to understand `p:first-child`. We strongly recommend you do not try to polyfill this, but if you do need one, you can use [Selectivizr](http://selectivizr.com/).
-
-#### When you sunset IE6 support, you can use:
-
-* `tr > td` : Immediate descendant (child) selector.
-* `dt + dd` : next sibling selector*
-* `dt ~ dd` : any following sibling
-* `div[attr]` and `img[src$=png]` : Attribute selector (starts with, ends with, contains).
-* `p:first-child`*
-* `div:hover` and `:hover` state on all non-`<a>`'s
-* `li.food.vegetable` : without worrying about the [chained classes bug](https://paulirish.com/2008/the-two-css-selector-bugs-in-ie6/)
-
-\* IE7-8 don't update styles properly when elements are manipulated with JS. Usually you have to force the browser to redraw (e.g. hide and show parent element).
-
-#### When you sunset IE7 support, you can use:
-
-* ` :before, :after` and generated content
-* `:focus` for elements with current focus
-* <a href="https://www.w3.org/TR/selectors/#lang-pseudo">`:lang(C)`</a> which targets an element based on language
+Most CSS Selectors are supported from IE8 onwards, so you should be safe to use them. But do note that, on browsers that do not support these selectors, a whole rule will be detected as invalid if these unsupported selectors are present. For example, in IE6 `#main, p:first-child {}` would be invalid because it is unable to understand `p:first-child`. We strongly recommend you do not try to polyfill this, but if you do need one, you could use [Selectivizr](http://selectivizr.com/).
 
 #### When you sunset IE8 support, you can use:
 
 * These very useful selectors: <a href="https://css-tricks.com/how-nth-child-works/">`:nth-child(n)`</a>, `:last-child`, `:target`, `:not(s)`, `:enabled`, `:disabled`, `:checked`, `::selection`
 * These ones, too: `:root`, `:nth-last-child(n)`, `:nth-of-type(n)`, `:nth-last-of-type(n)`, `:first-of-type`, `:last-of-type`, `:only-child`, `:only-of-type`, `:empty`
 
 <!--
-
-Resources:
-
-* https://www.smashingmagazine.com/2009/10/css-differences-in-internet-explorer-6-7-and-8/
-* http://www.bennadel.com/blog/2306-What-CSS-Properties-Are-Supported-When-You-Drop-IE6-Support.htm
-* http://analogysoft.com/learning/ui-hulk-out/#beyondie6
-* http://msdn.microsoft.com/en-us/library/cc351024(v=vs.85).aspx#selectors
-* http://www.quirksmode.org/css/contents.html
-* http://www.impressivewebs.com/browser-support-css3-selectors/
-
 	[].forEach.call( document.querySelectorAll('td'), function(elem){
 	  if (elem.innerText.trim() == 'No') elem.style.backgroundColor = 'red';
 	  if (elem.innerText.trim() == 'Yes') elem.style.backgroundColor = 'green';
 	});
-
 -->

posts/websockets.md

@@ -18,7 +18,7 @@ To make websockets easier to use there are multiple server-side framework soluti
 
 [Sockjs](https://github.com/sockjs) is one a framework which emulates the WebSocket API in browsers and has server implementations for node.js, Ruby, Erlang or tornado.
 
-[Socket.io](http://socket.io/) is a Node.js framework that helps with downlevel transports for browsers lacking native WebSocket support (and supports IE6+).
+[Socket.io](https://socket.io/) is a Node.js framework that helps with downlevel transports for browsers lacking native WebSocket support (and supports IE9+).
 
 XSockets is a .NET+JavaScript framework that handles fallback via Flash and Silverlight.
 

src/js/script.js

@@ -11,8 +11,8 @@ if (document.body.innerText) {
 }
 
 // gtieX augments. so a search is matching .gtie8,
-// need to match .gtie7 and .gtie6 too
-var ies = ['gtie6', 'gtie7', 'gtie8', 'gtie9', 'gtie10'];
+// need to match .gtie7 too
+var ies = ['gtie7', 'gtie8', 'gtie9', 'gtie10'];
 
 
 var search = document.getElementById('livesearch');