The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
You've posed an interesting question, one that I am in no position to answer.
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
Damnit. I just authorized a team to develop a browser specific implementation to make sure the freaking Safari don't mess up the roll out. Anyway it's a mini project, an utility. But my boss would recognize my ignorance with this wrong approval.
Instead of actively blocking certain browsers, they should just support a specific browser/browser engine (and version), say as much on their help/about page, and let the rest of the users be subjected to the whims of the HTML/CSS gods.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
It is what Microsoft decided to put there...
It is the same for almost all the modern browsers...
Instead of identifying the browser it list a kind-of compatibility list...
The reason for that is that they really do not want you to identify the browser (as a developer)...
"The only place where Success comes before Work is in the dictionary." Vidal Sassoon, 1928 - 2012
At least, one time in the past, MS supported different methods of doing things than other browsers (such as AJAX) and used a different rendering engine with different compatibilities with respect to HTML/CSS
Then, in one of the last incarnation of IE (where it had that name) they changed it so it couldn't be identified as IE because they were making the changes to fall in line (sort of) with other browsers. If they were identified as IE it would then mess things up.