Jonas asserts that " we can simply remove any code from necko that prompts." (bug 676059 comment 5). I assume we may want to chop this up into smaller bugs, hence the meta-bug. So we need a bug to remove prompts fpr "unsafe" redirects (and not follow them). What other cases are we talking about? What about when you go back in history to a POST? Others? I'm assuming you're not including basic auth :)

Basic auth should use an error page not a prompt where possible (I'm not sure what we'd want to do about non-page requests), but certainly the prompt should be tab-modal as alerts are today. There's the famous POSTDATA prompt, and I'm not sure about others.

(In reply to comment #0) > So we need a bug to remove prompts fpr "unsafe" redirects (and not follow > them). What other cases are we talking about? I think we should aim for removing all prompting from Necko. > What about when you go back in history to a POST? This prompt can/should be moved to the history code, for the cases where it can't be prevented. There are existing bugs to change the back/forward behavior such that the POSTDATA prompt will go away and/or be needed less. > I'm assuming you're not including basic auth :) If we implement bug 567804 and related bugs, the prompting would get moved from Necko to somewhere more appropriate.

stale tracker.. just one open dep