Unload: update outdated example

[arthurvr]

Would fix #388.

[mgol]

I'd also add a note that in Firefox (and maybe in some other places?) a message is ignored.

[arthurvr]

I'd also add a note that in Firefox (and maybe in some other places?) a message is ignored.

I thought about it, but are jQuery API docs the right place to teach people JavaScript? This isn't a jQuery specific behaviour.

[mgol]

We're already making this event special by setting returnValue by ourselves; people using the event directly have to know that. Since we're taking some responsibility off users, I think we should inform them we're not fixing everything. :)

What do you think, @dmethvin?

[dmethvin]

s/alert/message/ maybe?

s/will be/may be/ as well?

[dmethvin]

I believe we've gotten bug reports about this in the past, so perhaps we can add something to the warning already there.

[arthurvr]

Just for the reference, dropping in jquery/learn.jquery.com#608 too. Might be worth it to mention it there.

[arthurvr]

I believe we've gotten bug reports about this in the past, so perhaps we can add something to the warning already there.

Added a sentence warning about it. I don't think we should go in-depth. @dmethvin What do you think?

[mgol]

A tab? ;)

[arthurvr]

whoops! Fixed!

[arthurvr]

@mzgol Does the rest LGTY?

[mgol]

What about the info that some browsers will ignore the message at all?

[dmethvin]

I agree the comments here should be kept simple and not go too deep. It's always a bit frustrating when an API reference turns into a big "how to write JavaScript in the browser" article. Fortunately this page is pretty short at this point so we're not adding that much more to read.

This event is available so that scripts can perform cleanup when the user leaves the page.

This is a great point, maybe move this to the beginning in its own paragraph? That brings up the async operation trap, so perhaps add a sentence after it like, "Note that the browser may cancel or deny asynchronous operations attempted in this handler, such as AJAX or setTimeout."

Depending on the browser, the message you return will be used in a confirmation dialog.

Maybe something like this instead? "The string you return may be used in a browser confirmation dialog, but not all browsers support this." The warning already covers this ground again so I don't think we need much more.

[mgol]

@dmethvin That sounds good. :)

Michał Gołębiowski

[arthurvr]

@mzgol @dmethvin Updated PR.

[dmethvin]

LGTM!