3 ms·

I want to start by saying, this article needs a giant dose of grain-o-salt. The PS4 was leaked like how many times? And, we all know how that went. However, A

by bargl 14y ago

I want to start by saying, this article needs a giant dose of grain-o-salt. The PS4 was leaked like how many times? And, we all know how that went. However, As someone who is locked into an app that is tied to IE 6-7, I don't relish the idea of being forced to re-write some 50,000+ lines of legacy code. This does however force our customers to seriously consider putting out an effort to redesign in the first place.

tanzam75 14y ago
> I don't relish the idea of being forced to re-write some 50,000+ lines of legacy code. You don't have to. Simply set the DOCTYPE to force IE7 quirks mode. This move is clearly intended to improve compatibility with Internet applications.
- bargl 14y ago
  Isn't that what the article is talking about... I.E. this could break a lot of custom CSS within our application. Anything that is hacky and works with ie 6-8 will need to be redone. Is that right or did I read the premise of this article completely wrong? I know you are right for IE 9/ IE 10, but if they change IE 11 to force us to redo our CSS then... that sucks (but is kinda good too cuz I hate the legacy crap code we have).
  - tanzam75 14y ago
    The article said that the user-agent string was changing -- it said nothing about quirks mode going away. If you have an IE6-only intranet application, then by definition you are not depending on user-agent sniffing. In that case, you depend on the continued availability of quirks mode -- not on the user-agent string. If you have an intranet application that uses user-agent sniffing to support both legacy IE and standards-compliant browsers, then you should simply do nothing. The change in the user-agent string will cause Internet Explorer 11 to be treated as a "like Gecko" browser. This is as it should be, as IE 11 is a standards-compliant browser.
    - bargl 14y ago
      Thanks man! After doing some research on the User Agent (of which I was woefully uninformed) I've found out that I have more research to do...

by bargl 14y ago

tanzam75 14y ago

> I don't relish the idea of being forced to re-write some 50,000+ lines of legacy code. You don't have to. Simply set the DOCTYPE to force IE7 quirks mode. This move is clearly intended to improve compatibility with Internet applications.

bargl 14y ago
Isn't that what the article is talking about... I.E. this could break a lot of custom CSS within our application. Anything that is hacky and works with ie 6-8 will need to be redone. Is that right or did I read the premise of this article completely wrong? I know you are right for IE 9/ IE 10, but if they change IE 11 to force us to redo our CSS then... that sucks (but is kinda good too cuz I hate the legacy crap code we have).
- tanzam75 14y ago
  The article said that the user-agent string was changing -- it said nothing about quirks mode going away. If you have an IE6-only intranet application, then by definition you are not depending on user-agent sniffing. In that case, you depend on the continued availability of quirks mode -- not on the user-agent string. If you have an intranet application that uses user-agent sniffing to support both legacy IE and standards-compliant browsers, then you should simply do nothing. The change in the user-agent string will cause Internet Explorer 11 to be treated as a "like Gecko" browser. This is as it should be, as IE 11 is a standards-compliant browser.
  - bargl 14y ago
    Thanks man! After doing some research on the User Agent (of which I was woefully uninformed) I've found out that I have more research to do...