Microsoft stupid alerts, they'll never get a clue

That is pretty funny! Stupid alerts hehe

Hate to break it to you, but it's no Microsoft's fault, it's Apple. They've some bugs in the way they handle certain javascript functions...

http://episteme.arstechnica.com/eve/forums/a/tpc/f/48409524/m/975001011831

@Mike: all I see in that page is back and forth argument between fanboys of either camps, I didn't find any rationale explanation why you have:
- a function in MS code (not Apple's) perfectly detecting that I'm trying to close the window
- a dialog created by MS (not Apple) that asks me if I really want to close that window. Because, you know, I might be a stupid user (just like in pure Windows tradition).

Never seen that anywhere else but on a MS site. Coïncidence, Apple's fault? Don't believe it, sorry.

I don't mean to be disrespectful, but I guess you can't read code and/or aren't a software engineer.

The dialog box comes from Safari, plain and simple. The function is in javascript, which is a standard. So it's Apple's job to properly handle the interpretation of standard script in their browser. They don't. Other sites have this problem too. Just do a search for that term "are you sure you want to navigate away from this page."

I didn't mean to piss on your rant, but I just thought you want your facts right. It's cool if you don't.

Well Mike, I'm no software engineer but I can read code. I also spend hours a day surfing the net for my job and that's the first time I see this alert in Safari. Too bad it was on a Microsoft property.

Now, looking for it on the web gives me this :

http://msdn.microsoft.com/workshop/author/dhtml/reference/events/onbeforeunload.asp

Which references the onbeforeunload handler for JScript and Visual Basic Scripting Edition (VBScript) 5.0 or later in Internet Explorer, and says: "The default statement that appears in the dialog box, "Are you sure you want to navigate away from this page? ... Press OK to continue, or Cancel to stay on the current page.", cannot be removed or altered."

So, ok for the standard ECMAscript function. Now how come Soapbox is able to serve me a CSS file for Safari - which means they do browser sniffing and have customized a CSS for Safari (it's in the name of the file) - and not get around that "bug"? Or is it a bad use of the handler, as suggests this page: http://www.squarefree.com/securitytips/mozilla-developers.html
“Avoid adding dialogs where the safe response on a malicious site is "Yes", such as onbeforeunload's "Are you sure you want to navigate away from this page?"”?