<story><title>Microsoft Edge</title><url>https://github.com/MicrosoftEdge/MSEdge</url></story><parent_chain><item><author>phkahler</author><text>&amp;gt;&amp;gt; our unique web-platform codebase still faces occasional compatibility problems as web developers focus less on HTML standards and rationally focus on widely used platforms like Chrome to develop and validate experiences for their customers&lt;p&gt;IMHO this is not rational on the part of web developers. If they&amp;#x27;ve forgotten the lessons of IE-6 they need to have a refresher and stick to standards. If that means sticking to a subset of the standards that are supported by all browsers then so be it - stop thinking about yourself and your immediate desire (it&amp;#x27;s not a need after all) and think about the future and your users.</text></item></parent_chain><comment><author>le-mark</author><text>I&amp;#x27;m just finishing up a year+ project to make an old IE7 app work on Chrome&amp;#x2F;Firefox. IE7 is the oldest version that IE11 supports in compatability mode. As it stood, this old app was actually quite impressive. It was a true SPA before SPAs were a thing (2005 or so). It used all the Microsoft specific tech; DHTML, behaviors, htc components, soap&amp;#x2F;xml, client side xpath&amp;#x2F;xsl&amp;#x2F;xslt. Thankfully only a little activex that was easy to replace. Rewriting wasn&amp;#x27;t an option, but even putting in shims and reorganizing the code was a major effort.&lt;p&gt;Realistically, that&amp;#x27;s a worst case scenario, and I think it would be a long time before firefox&amp;#x2F;Chrome diverged to that level, if at all.&lt;p&gt;But the horror, oh the horror....</text></comment>
<story><title>Microsoft Edge</title><url>https://github.com/MicrosoftEdge/MSEdge</url></story><parent_chain><item><author>phkahler</author><text>&amp;gt;&amp;gt; our unique web-platform codebase still faces occasional compatibility problems as web developers focus less on HTML standards and rationally focus on widely used platforms like Chrome to develop and validate experiences for their customers&lt;p&gt;IMHO this is not rational on the part of web developers. If they&amp;#x27;ve forgotten the lessons of IE-6 they need to have a refresher and stick to standards. If that means sticking to a subset of the standards that are supported by all browsers then so be it - stop thinking about yourself and your immediate desire (it&amp;#x27;s not a need after all) and think about the future and your users.</text></item></parent_chain><comment><author>criddell</author><text>&amp;gt; stick to standards&lt;p&gt;There are standards, and then there are standards.&lt;p&gt;Ideally, de jure standards would rule the day but in practice de facto standards often win.</text></comment>