<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: You can improve IE.next</title>
	<atom:link href="http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/</link>
	<description>Working together for standards</description>
	<lastBuildDate>Wed, 27 Mar 2013 12:19:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Turkey Cheap Holidays</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-65878</link>
		<dc:creator>Turkey Cheap Holidays</dc:creator>
		<pubDate>Thu, 27 Mar 2008 01:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-65878</guid>
		<description>DADesigners. is compiling a list of css errors found in internet explorer 7</description>
		<content:encoded><![CDATA[<p>DADesigners. is compiling a list of css errors found in internet explorer 7</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Allen Garner</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-61558</link>
		<dc:creator>Allen Garner</dc:creator>
		<pubDate>Wed, 20 Feb 2008 00:19:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-61558</guid>
		<description>Security and Support for css Standards is definately at the top of the list for example the select element in Internet Explorer 7 still does not support many css implementaions.  Also, we need to start thinking about the web more in terms of programming. The internet has been and is increasingly more so being used as an alternative solution for applications in intranets and in webpages on the internet. We need to add native elements to html such as datagrid combo boxes , tab structures, color pickers, date/time pickers, hierarchical tree structures and many other useful elements that will aid in the improvement and usability of the internet.</description>
		<content:encoded><![CDATA[<p>Security and Support for css Standards is definately at the top of the list for example the select element in Internet Explorer 7 still does not support many css implementaions.  Also, we need to start thinking about the web more in terms of programming. The internet has been and is increasingly more so being used as an alternative solution for applications in intranets and in webpages on the internet. We need to add native elements to html such as datagrid combo boxes , tab structures, color pickers, date/time pickers, hierarchical tree structures and many other useful elements that will aid in the improvement and usability of the internet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alex</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-55117</link>
		<dc:creator>Alex</dc:creator>
		<pubDate>Mon, 12 Mar 2007 03:23:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-55117</guid>
		<description>What I&#039;d like to see is visually see a td with a colspan or rowspan attribute (kind of like how Firefox displays td tags with &quot;rowspans&quot; and &quot;colspans&quot;). Otherwise, a table might look ugly and seem like there was nothing filling its spot.</description>
		<content:encoded><![CDATA[<p>What I&#8217;d like to see is visually see a td with a colspan or rowspan attribute (kind of like how Firefox displays td tags with &#8220;rowspans&#8221; and &#8220;colspans&#8221;). Otherwise, a table might look ugly and seem like there was nothing filling its spot.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sanyodenki</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-43836</link>
		<dc:creator>sanyodenki</dc:creator>
		<pubDate>Wed, 07 Feb 2007 14:09:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-43836</guid>
		<description>1. Make it CSS 2.1 standards compliant. 
DON’T ADD ANYTHING until you fix all the broken and unfinished stuff FIRST. IE is a half-baked, defective product. It doesn’t need “new stuff”. It needs to work right first.</description>
		<content:encoded><![CDATA[<p>1. Make it CSS 2.1 standards compliant.<br />
DON’T ADD ANYTHING until you fix all the broken and unfinished stuff FIRST. IE is a half-baked, defective product. It doesn’t need “new stuff”. It needs to work right first.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Golding</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-43610</link>
		<dc:creator>Dave Golding</dc:creator>
		<pubDate>Wed, 07 Feb 2007 00:53:10 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-43610</guid>
		<description>It shouldn&#039;t be all that difficult to fix CSS measures, given that Firefox is open source and all the web standards are visible to everyone. Just copy and paste the rendering engine from Firefox into IE, and we&#039;re good. Heck, you do that with everything else (e.g. Word =&gt; WordPerfect, Excel =&gt; Lotus, Windows =&gt; Mac, Internet Explorer =&gt; Netscape Navigator, Zune =&gt; iPod, X-Box =&gt; Playstation).</description>
		<content:encoded><![CDATA[<p>It shouldn&#8217;t be all that difficult to fix CSS measures, given that Firefox is open source and all the web standards are visible to everyone. Just copy and paste the rendering engine from Firefox into IE, and we&#8217;re good. Heck, you do that with everything else (e.g. Word =&gt; WordPerfect, Excel =&gt; Lotus, Windows =&gt; Mac, Internet Explorer =&gt; Netscape Navigator, Zune =&gt; iPod, X-Box =&gt; Playstation).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Juergen Riemer</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-43415</link>
		<dc:creator>Juergen Riemer</dc:creator>
		<pubDate>Tue, 06 Feb 2007 15:13:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-43415</guid>
		<description>&gt;&gt;&gt; native support of SVG </description>
		<content:encoded><![CDATA[<p>&gt;&gt;&gt; native support of SVG</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Lascurettes</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-43103</link>
		<dc:creator>John Lascurettes</dc:creator>
		<pubDate>Mon, 05 Feb 2007 21:39:08 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-43103</guid>
		<description>I would like to second Thomas Tallyce&#039;s comment (&lt;a href=&quot;#comment-10736&quot; rel=&quot;nofollow&quot;&gt;#22&lt;/a&gt;) that says hasLayout needs to be refactored. A majority of Explorer&#039;s more persistent bugs and shortcomings are directly tied to this behavior.</description>
		<content:encoded><![CDATA[<p>I would like to second Thomas Tallyce&#8217;s comment (<a href="#comment-10736" rel="nofollow">#22</a>) that says hasLayout needs to be refactored. A majority of Explorer&#8217;s more persistent bugs and shortcomings are directly tied to this behavior.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jack Sleight</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-43045</link>
		<dc:creator>Jack Sleight</dc:creator>
		<pubDate>Mon, 05 Feb 2007 17:54:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-43045</guid>
		<description>I&#039;ve run into this CSS bug a number of times, unfortunately it was never fixed in IE7. A fix would be fantastic:

http://rowanw.com/bugs/overflow_relative.htm
http://mt-olympus.com/emmett/bug_overflow_positionrelative.php</description>
		<content:encoded><![CDATA[<p>I&#8217;ve run into this CSS bug a number of times, unfortunately it was never fixed in IE7. A fix would be fantastic:</p>
<p><a href="http://rowanw.com/bugs/overflow_relative.htm" rel="nofollow">http://rowanw.com/bugs/overflow_relative.htm</a><br />
<a href="http://mt-olympus.com/emmett/bug_overflow_positionrelative.php" rel="nofollow">http://mt-olympus.com/emmett/bug_overflow_positionrelative.php</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Painfully Obvious &#187; Blog Archive &#187; Link: Talking with Microsoft about IE.next</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-42957</link>
		<dc:creator>Painfully Obvious &#187; Blog Archive &#187; Link: Talking with Microsoft about IE.next</dc:creator>
		<pubDate>Mon, 05 Feb 2007 14:25:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-42957</guid>
		<description>[...] Talking with Microsoft about IE.next. The things he asked for (mostly JS-related) were determined (by vote) to be the most critical things for IE to catch up on. I&#8217;m optimistic. [...]</description>
		<content:encoded><![CDATA[<p>[...] Talking with Microsoft about IE.next. The things he asked for (mostly JS-related) were determined (by vote) to be the most critical things for IE to catch up on. I&#8217;m optimistic. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Talking with Microsoft about IE.next &#172; Easy Reader</title>
		<link>http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/comment-page-2/#comment-42625</link>
		<dc:creator>Talking with Microsoft about IE.next &#172; Easy Reader</dc:creator>
		<pubDate>Sun, 04 Feb 2007 20:50:33 +0000</pubDate>
		<guid isPermaLink="false">http://www.webstandards.org/2006/11/04/you-can-improve-ie-next/#comment-42625</guid>
		<description>[...] You may recall that the DOM Scripting and Microsoft task forces, in collaboration with JS Ninjas, had been compiling a list of issues, needs, and wants for IE.next over the last few months (a list many of you contributed to as well, via your feedback). The list was to focus on what we wanted to see happen in terms of JavaScript support (as IE7 didn&#8217;t get much of an update in that area), but when it came down to it, there were other areas we really felt needed some love. [...]</description>
		<content:encoded><![CDATA[<p>[...] You may recall that the DOM Scripting and Microsoft task forces, in collaboration with JS Ninjas, had been compiling a list of issues, needs, and wants for IE.next over the last few months (a list many of you contributed to as well, via your feedback). The list was to focus on what we wanted to see happen in terms of JavaScript support (as IE7 didn&#8217;t get much of an update in that area), but when it came down to it, there were other areas we really felt needed some love. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic page generated in 0.355 seconds. -->
<!-- Cached page generated by WP-Super-Cache on 2013-05-02 12:50:53 -->