Safari has it and given the fact that we only recently switched from Ctrl-Q to Crtl-W for closing tabs, people might accidentally hit Ctrl-Q when they want to close just the tab. It happend to me at least. So for now I would keep it.
Elinks uses CTRL-C to close tabs. It's kind of tough to think CTRL-Q closes a tab to begin with. Mistake for "close qab" just doesn't sound right to begin with. However, if CTRL-C was mapped to quit, aka "close application", well that would be confusing. Or if "CTRL-Q" were on a keyboard layout next to the "CTRL-C" But still, ELinks does ask to quit before quiting. But this is because I keep typing ":q" (VIM quit), and 'q' is mapped to quit in ELinks. (But this is user error, as I start thinking I'm within VIM at times due to all the console text.) So, some good examples when there's no conflict, and some examples where there is a conflict. Really, when asking, you're just trying to prevent user error. However, how would you like a prompt on your vehicle every time you pressed the brakes? Do you really want to stop? Or, how about every time you start your vehicle and you're within an emergency situation and get, "Do you really want to start your car?" With real world applications, security of preventing accidental quitting is application response to users intentions. <shrugs> I'm sure this has been debated quite a bit, and with Windows, I get so many prompts that I become non-productive & frustrated. -- Roger http://rogerx.freeshell.org/