Recently, the firefox crew offered a new version of its browser doing a large version jump to 1.5. Sound great, but some new problems are included.
To prevent stressing client systems scripts are for responding, it includes server-side as well as client-side scripts. If no output is created for about ten seconds a trap is triggered offering the user a decision possible to interrupt the currently running script or give it another try. However, this is a more comfortable way to prevent system starvation instead of killing the running application. But, uploading a file containing some hundred kilobytes such as zip archives and postprocessing them via php on the webserver takes even some more time. This will result in stressing the user instead of the system. Because, after given the script another try, the decision will be triggered periodically. If anyone knows the configuration attribute to change the responding timelimit, please let me know asap.
However, I know a possible solution would be to flush some output each second to prevent this situation. But this is almost impossible, when using a template engine such as smarty without producing additional page reload which whould stop prior script invocations.
To mention another interesting problem (not new): Popup windows created by firefox can be ignored, by clicking in the background – the active window will change immediately back to firefox. I think it is not intended, because it is mandentory to give an answer. Furthermore, mouse events on popup windows are redirected to the displayed website, thus unexpected behaviour may be provoked and could be used for unintended actions. This may be a problem in the internal extension handling, because I am not sure if this behaviour currently works on all firefox-own popup windows.