User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+ Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b3) Gecko/20050712 Firefox/1.0+ Can a cancel button be added to the update download screen so that the user be allowed to cancel a update download in progress if required (a user may have some reason to do so, the one below being an example but not the reason, so please dont do a "This is a Alpha dude" reply) I had filed a update bug report here https://bugzilla.mozilla.org/show_bug.cgi?id=300903 that was closed as invalid shortly there after. But before that, I was asked to update the url in about:config if I wanted to desperately check updates for my just downloaded Deer Park Alpha 2. https://aus-staging.mozilla.org:8711/update2/0/%PRODUCT%/%VERSION%/%BUILD_ID%/%BUILD_TARGET%/%LOCALE%/update.xml Me, being the idiot that I am, actually did so to find "Deer Park 1.0+" being recommended "highly", for security reasons (I Think). Me being the stupid that I am, actually clicked on the update / download button only to find that I could not cancel it. The update screen now says that the 7.4MB update is now complete and will need a restart to be applied. (after doing my course in Industrial Design, I have got this habit of clicking on every link possible to check out what happens, just like a monkey on steroids jumping about for the heck of it) PS: I promise I will not look for any more bugs / enhancements in Alpha version s after this. Promise Reproducible: Always Steps to Reproduce: 1. Click on Help -> Update and check for updates 2. Assuming you have updates available (which is not true right now), click on the download / update option (forgot which one exactly) 3. For whatever reason that may lead you to so, try to stop the update downlosd in progress. You just can't, simple. Actual Results: Deer Park Alpha 2 completed downloading 7.4 MB "Deer Park 1.0+" update. There was no "intutive" way to stop it. Expected Results: Provide a "Cancel" option to stop the update download in progress.
*** This bug has been marked as a duplicate of 300922 ***