31–40 of 70 posts
Dear Microsoft, other browser vendors release new versions on a regular basis, regardless of the operating system number. This enables browser-related technologies to evolve at a more rapid pace. So please do us all a favor and stop locking major IE releases to Windows versions and just try to imitate what others do. We won't judge you for copying, promise. Sincerely, Web developers
Dear Microsoft, other browser vendors release new versions on a regular basis, regardless of the operating system number. This enables browser-related technologies to evolve at a more rapid pace. So please do us all a favor and stop locking major IE releases to Windows versions and just try to imitate what others do. We won't judge you for copying, promise. Sincerely, Web developers
Dear Microsoft, other browser vendors release new versions on a regular basis, regardless of the operating system number. This enables browser-related technologies to evolve at a more rapid pace. So please do us all a favor and stop locking major IE releases to Windows versions and just try to imitate what others do. We won't judge you for copying, promise. Sincerely, Web developers
please stop arbitrarily bumping your version numbers so you don't have to hear complaints about open source contributions being ignored. Do you seriously expect us to believe you got through 25 real, full versions in 4.5 years?
Sincerely, "one guy not trying to talk for everyone".
Earlier quoted context omitted.
There are several situations where a web app has no choice but to rely on the user agent string to vary its behavior. For example, when you let a user download a file, you usually send a header such as: Content-Disposition: attachment; filename=FILENAME But what do you do if the filename contains non-ASCII characters? There are RFCs, but every browser has its own rules about encoding, and IE is especially problematic…
I understand the point about browser-specific instructions, but using the User-Agent to decide how to encode a file name sounds…wrong. Imagine your email client checking the email client of the recipient to decide how to encode the file name of the file you attached – sure, it’s nice if it is possible, but in general, standards are supposed to be, well, standards, and not caring about broken software might help motiv…
Dear Microsoft, other browser vendors release new versions on a regular basis, regardless of the operating system number. This enables browser-related technologies to evolve at a more rapid pace. So please do us all a favor and stop locking major IE releases to Windows versions and just try to imitate what others do. We won't judge you for copying, promise. Sincerely, Web developers
Is this because it is tied to Window Explorer (the Windows file system)? Or is it because the developers are dense.
Earlier quoted context omitted.
I meant 'who does check that user agent', edited to clarify.
A lot of people, on Firefox OS we have a blacklist of sites we have to send Android like user agents to so we are served mobile friendly content: https://github.com/mozilla-b2g/gaia/blob/master/build/ua-ove... Its a sad situation.
> Microsoft also included the command "Like Gecko" which instructs the website to send back the same version of the website as they would to Firefox seriously, who does that? 'msie5.0 mozilla', good times. 'like gecko' => msie trying to look like webkit, who tries to look like firefox. yeah, makes perfect sense. could anyone give an example of a modern application that checks against the user agent string?
This version of IE (11) comes from the leaked Windows Blue build 9364. What you might want to consider is how MS real world test IE11 without broadcasting the user agent. I'm guessing this 'beta' version is reporting itself as Firefox to disguise itself from server logs.