Open
Bug 410397
Opened 17 years ago
Updated 2 years ago
Try Again button disabled after press and then press stop
Categories
(Core :: DOM: Navigation, defect)
Tracking
()
NEW
People
(Reporter: kyferez, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2007123005 Minefield/3.0b3pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9b3pre) Gecko/2007123005 Minefield/3.0b3pre If a web page does not load, and the try again button appears, and you then click on try again, and then click on stop, the try again button is still disabled. It should reenable so I can try again after pressing stop. This is critical for dialup users. Reproducible: Always Steps to Reproduce: 1. Have a page not load 2. Click Try Again 3. Before it can connect to the webserver, click stop. 4. The Try again button is still disabled. Expected Results: The try again button should re-enable after clicking stop. Personally, I detest that the Try Again button is disabled after clicking it. Why? Because I'm stuck on dialup, and if I'm trying to load several pages at a time, I can tell when one isn't going to connect to the website well before it times out (after it timed out the first time) and want to go ahead and click try again for a second time. However I can't. I have to additionally click stop before clicking try again for a second time. Grrr.
Updated•17 years ago
|
Component: General → Embedding: Docshell
Product: Firefox → Core
QA Contact: general → docshell
Comment 1•17 years ago
|
||
Hmm. The problem is that the error page doesn't have a good way to detect the fact that Stop got pressed. Perhaps docshell should fire some sort of event at the page if it gets an NS_BINDING_ABORTED stop code and is currently showing an error page, so the button can be reenabled? biesi, jst, what do you think? Gavin, you want to try doing that?
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•17 years ago
|
||
Sounds reasonable to me. If we fire it only at error pages, I don't so much care about what the event is etc, as it should never leak out to web pages etc.
Comment hidden (spam) |
Updated•2 years ago
|
Flags: needinfo?(majelispena)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•