User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:2.0b12pre) Gecko/20110217 Firefox/4.0b12pre Build Identifier: Mozilla/5.0 (Windows NT 6.1; rv:2.0b12pre) Gecko/20110217 Firefox/4.0b12pre Example I visit "YouTube" and then a page appears in front of me saying that the web page is blocked but there is an option button to continue loading to the site and I click It, After a while like whenever the internet cuts and reconnects , the message appears again. So My request it to Get Firefox to remember my option (continue) clicked previously. Reproducible: Always Expected Results: Remember My Option Clicked Forever I live in a school where their firewall have constant blocks to specific sites but a few of them have an option to continue like YouTube and Firefox website. The problem Is that I have to click continue all the time the internet refreshes or reconnects or even sometimes reloads. So Making Firefox remember that option would be awesome . Check the picture in the attachment for the kind of message and what I meant.
Created attachment 513438 [details] the continue button in the message has to be clicked frequently. Instead make firefox capable of remembering
this conflicts with the minefield update policy
I've also seen a Lot of students here shifting to chrome mostly because they say that firefox is buggy and not smooth as chrome is and I have had times where Firefox doesn't quit immediately when installing updates for it hence preventing it from installing Running in background
Not a bug with Firefox, unless this somehow works in Chrome but doesn't in Firefox. Firefox cannot just change random website functionality - the website (or in this case the Intranet proxy landing page) needs to be modified by whomever manages your network/proxy.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INVALID
Version: unspecified → Trunk
If it helps, use something like Scriptish (a fork of Greasemonkey) to modify the page client-side to save having to continually click the button manually.
You need to log in before you can comment on or make changes to this bug.