Finally IE issue
-
One of the other developers at work today finally had a problem with ajax not working right in IE... but worked in every other browser (Firefox, Chrome, Safari, Opera). It was because of that "User Agent" string that IE 10 & 11 passes (the site worked in IE9 fine). If they are going to say they are "Mozilla" shouldn't they at least have it work in Mozilla compatible code is passed back from IIS? We installed a "patch" on our dev server and it finally worked after a reboot. We can't just reboot our live server whenever we want to install this patch (we have many financial transactions per minute). The thing that makes me the maddest is that why use "Mozilla" user agent string if your not to web standards like Mozilla? Microsoft doesn't have a clue what standards are. I use IE to test sites and to download firefox when I get a new machine. That is about the only thing it's good for. It's bad that open source browsers/servers can stay more compliant to web standards than a company that has billions to spend. That is my rant for the day :)
-
One of the other developers at work today finally had a problem with ajax not working right in IE... but worked in every other browser (Firefox, Chrome, Safari, Opera). It was because of that "User Agent" string that IE 10 & 11 passes (the site worked in IE9 fine). If they are going to say they are "Mozilla" shouldn't they at least have it work in Mozilla compatible code is passed back from IIS? We installed a "patch" on our dev server and it finally worked after a reboot. We can't just reboot our live server whenever we want to install this patch (we have many financial transactions per minute). The thing that makes me the maddest is that why use "Mozilla" user agent string if your not to web standards like Mozilla? Microsoft doesn't have a clue what standards are. I use IE to test sites and to download firefox when I get a new machine. That is about the only thing it's good for. It's bad that open source browsers/servers can stay more compliant to web standards than a company that has billions to spend. That is my rant for the day :)
-
Quote:
Finally IE issue
I know what you mean. I never had a problem with IE until I tried to use it.
There are only 10 types of people in the world, those who understand binary and those who don't.
-
We normally have to do little work arounds here and there for minor things but this issues didn't allow the whole page to work. A page written in .NET, served by IIS, and tested with IE. 3 MS things that obviously don't always work together :) LOL
rriegel wrote:
A page written in .NET, served by IIS, and tested with IE. 3 MS things that obviously don't always work together :) LOL
:laugh:
The report of my death was an exaggeration - Mark Twain
Simply Elegant Designs JimmyRopes Designs
I'm on-line therefore I am. JimmyRopes -
One of the other developers at work today finally had a problem with ajax not working right in IE... but worked in every other browser (Firefox, Chrome, Safari, Opera). It was because of that "User Agent" string that IE 10 & 11 passes (the site worked in IE9 fine). If they are going to say they are "Mozilla" shouldn't they at least have it work in Mozilla compatible code is passed back from IIS? We installed a "patch" on our dev server and it finally worked after a reboot. We can't just reboot our live server whenever we want to install this patch (we have many financial transactions per minute). The thing that makes me the maddest is that why use "Mozilla" user agent string if your not to web standards like Mozilla? Microsoft doesn't have a clue what standards are. I use IE to test sites and to download firefox when I get a new machine. That is about the only thing it's good for. It's bad that open source browsers/servers can stay more compliant to web standards than a company that has billions to spend. That is my rant for the day :)
Unfortunately, the "Mozilla" part of the user agent string has very little to with the modern work of the Mozilla foundation and more to do with legacy web servers not service up frames (remember frames?) back in like 1995. Since then, just in case a webserver is really really out of date pretty much all browsers' agent strings start with "Mozilla". So unfortunately, using the user agent to assume a set of features has been just plain unreliable for years now (http://learn.jquery.com/code-organization/feature-browser-detection/[^]). If you really want to know what the JavaScript engine is capable of you need to be doing feature detection within your JavaScript.
-
Unfortunately, the "Mozilla" part of the user agent string has very little to with the modern work of the Mozilla foundation and more to do with legacy web servers not service up frames (remember frames?) back in like 1995. Since then, just in case a webserver is really really out of date pretty much all browsers' agent strings start with "Mozilla". So unfortunately, using the user agent to assume a set of features has been just plain unreliable for years now (http://learn.jquery.com/code-organization/feature-browser-detection/[^]). If you really want to know what the JavaScript engine is capable of you need to be doing feature detection within your JavaScript.
What is a fact filled helpful reply doing in a blatant rant thread?
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
-
What is a fact filled helpful reply doing in a blatant rant thread?
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
It turns out that my own ranting skills might be rusty. I'm far too used to having to bite my tongue and then explain everything to the client. I blame my colleagues. Apparently its company policy to be helpful. Anyway. Agent sniffing is just not reliable. The ubiquity of the "Mozilla" prefix and the less popular but still prolific "like Gecko" suffix exist because agent sniffing wasn't helping the actual users. It hasn't been reliable for donkey's years and it does lead to just the kind of problem the OP ran into. Friends don't let other friends read the user agent string. My big issue with agent sniffing is that as a regular user of Internet Explorer, (Lumia 920 and Surface RT as well as good old desktop IE), it seems like almost every day I face a page that renders wrongly because someone wrote a website, either (still!!!) assuming that a browser identifying itself as "MSIE" is going to use the old IE6 box model; or perhaps they didn't check anything at all and just assumed that all browsers on a touch screen device are going to include JavaScript features only available to iPads. I also still have a Nexus-One for travelling with. That bad boy uses the "Android Browser" and it has almost no "modern" features despite it also having "Mozilla/5.0" at the beginning of its agent string. I do agree though that a reboot shouldn't have been required. It is vicious cruelty on the part of the web server vendor. Is that better? I'm a little worried, like I might have gone too far. I don't like to get overexcited like this. Right now I want to go and punch one of those gym punching bag things and then write a strongly worded letter to the local council about the state of some of the footpaths in my area.