Matthew Rath

My feedback

  1. 7,403 votes
    Sign in
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      You have left! (?) (thinking…)
      62 comments  ·  Microsoft Edge Developer » Miscellaneous  ·  Flag idea as inappropriate…  ·  Admin →

      On December 15th of 2011 Microsoft made a big change that largely goes unnoticed by the vast majority of users; updates to Internet Explorer began to happen automatically.

      Today, Microsoft continues to install the latest updates for Internet Explorer supported by the user’s operating system without getting in the way. With Internet Explorer 10 we also added a UI control to the “About Internet Explorer” window which gave the end-user easier control over this process.

      Understandably there are some situations in which auto-updates are not desired. For instance, enterprise customers may (and do) choose to opt-out of these updates due to a reliance upon older versions of Internet Explorer internally.

      Tasked with supporting legacy applications, while also supporting the advancing web, the Internet Explorer team developed Enterprise Mode for Internet Explorer 11. This feature is designed to grant the user all of the security and speed of a modern browser,…

      Matthew Rath commented  · 


      There is no auto-update feature inbuilt into older browsers please learn from the past, people that bought/installed:

      - WinXP, were using IE6/7 until support ended
      - Win7, were using IE7/8

      They were still using older versions of the browser despite improvements that may have been made through successive versions, easily downloadable why?

      Because in many cases they weren't forced to update. why?

      The only time they would even consider it is if the website dev in question wasn't taking previous versions into account and the experience of viewing online content was bad enough that they actively thought something was wrong with their computer. Of course the other option is, it paints us (the devs) in a bad light and they just believe it's the websites fault, "it's broken".

      On the flip side of the same scenario, assuming we were designing the ultimate of websites, for compatibility and UX... (which is the standard we work at) even taking into some of the previous IE's ridiculous conventions and semantics... MS MAKING WORK HARDER FOR US! why?

      For example: we dont care that you use web prefixes, look at -moz / -webkit... we can apply those with relative ease either through pre-compilers or hardcoding... why?

      Because they are RENDERED and BEHAVE in much the same manner across most browsers that implement them AND on where ever in the DOM we choose to implement them. why is this important?

      Because i can be assured that if i implement a -webkit style on a selector in css it's corresponding -moz prefix will BEHAVE in much the same way with very few exceptions (unless they're experimental features).

      In stark contrast, if i use IE proprietary prefix's not only do i have to retest in the original browsers once they're added (to make sure by some quirk they dont interfere), i also have to test in IE to make sure that some quirk doesnt cause it to be rendered in some other way in DOM because it is not consistent in rendering with other comparative prefixes. Got a bit off topic there but...

      We come full circle to 'how MS deploy their browsers / auto-updates'.

      Most browsers implement a stable / experimental release policy... nope not MS their default stance is 1 version to achieve it all, 1 version to find them, 1 version to rule them all and in the darkness bind them.

      It is this lack of version control and deployment strategy (stable / experimental) that has led to updates of fully fledged browser versions (and/or operating systems *cough windows 9,
      i mean 8.1 *cough) that:

      a. contain useless and/or deprecated features
      b. are not consistent in rendering the DOM to spec

      These problems could be solved merely by being able to keep the browser updated by default independent of O/S updates and user conciousness... why?

      Users are viewing content independent of it being on their machines initially (ignoring caches), should not the content viewer (browser) be kept as up to date with a stable release as possible independent of what O/S you have?

      I propose that IF the older versions cannot be made to auto-update, then at least IE11/12
      (or whatever your semantics dictate will be shipped with Windows10) have a restructured version control and deployment strategy to not only provide a better user experience but also a more robust developer platform that is more actively participated in and therefore more up to date with standards and more consistent with rendering and performance.

      Matthew Rath supported this idea  · 

    Feedback and Knowledge Base