Closed Bug 535672 Opened 16 years ago Closed 15 years ago

Stop button does not stop searches from the URL bar

Categories

(Firefox :: General, defect)

5 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: danweiss, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2b4) Gecko/20091124 Firefox/3.6b4 (.NET CLR 3.5.30729) If you type something in to the URL bar, realize you started a Search instead of selecting a URL, then immediately press Escape to stop it, the search looks like it is stopped, then proceeds to load anyway. Reproducible: Always Steps to Reproduce: 1. Type a search term into the URL bar which is not already in cache 2. Press ESCAPE multiple times to stop the page from loading Actual Results: The page continues to load anyway. Expected Results: The page should stop loading.
Related stuff: bug 529954 comment 1
What is going on with this? I've also tested Minefield, and it also has the same bug. I think it is unacceptable that the Stop button does not abort loading a page.
Version: unspecified → 3.6 Branch
WFM - Mozilla/5.0 (Windows NT 5.1; rv:7.0a1) Gecko/20110626 Firefox/7.0a1 ID:20110626030756 Reporter -> Are you still experiencing this issue with the latest version of Firefox 5? Does the issue occur with the latest nightly? http://nightly.mozilla.org/
I just tested this in Firefox 5, and the problem still happens. When searching from the search bar, no problem, the stop button stops the search like it should. But when typing in something into the address bar, pressing Enter to start a search, then immediately pressing ESC, it acts like it's stopping, but eventually loads the search page about half a second later.
Version: 3.6 Branch → 5 Branch
This seems to be fixed now.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.