Closed
Bug 364903
Opened 18 years ago
Closed 18 years ago
Problem loading page "Try Again" button doesn't dim once pressed
Categories
(Core :: DOM: Navigation, defect)
Core
DOM: Navigation
Tracking
()
RESOLVED
FIXED
People
(Reporter: L.Wood, Assigned: Gavin)
References
Details
Attachments
(1 file)
(deleted),
patch
|
neil
:
review+
bzbarsky
:
superreview+
|
Details | Diff | Splinter Review |
I'm on dialup and getting a lot of "Problem loading page" in-page alerts. So I'm thumping the "Try Again" button a lot in various tabs. But once I've pressed that button in a tab, how do I know that I've pressed that button and the browser's doing its best to reload the page? The button can be pressed again and again...
Once the button is pressed, it should dim or flatten (possibly via applying a style) until the page resets yet again and the button needs to be pressed by the user again.
(Not sure of the category here for this UI issue: form manager? file handling?)
Assignee | ||
Updated•18 years ago
|
Component: Form Manager → Embedding: Docshell
Product: Firefox → Core
QA Contact: form.manager → docshell
Version: unspecified → Trunk
Comment 1•18 years ago
|
||
Just an issue of the XUL on that page, no? I'd think that clicking the button should simply disable it.
Assignee | ||
Comment 2•18 years ago
|
||
Assignee: nobody → gavin.sharp
Status: NEW → ASSIGNED
Attachment #250198 -
Flags: superreview?(bzbarsky)
Attachment #250198 -
Flags: review?(neil)
Comment 3•18 years ago
|
||
Comment on attachment 250198 [details] [diff] [review]
patch
Yeah, like that. ;)
Attachment #250198 -
Flags: superreview?(bzbarsky) → superreview+
Assignee | ||
Updated•18 years ago
|
Whiteboard: [patch-r?]
Comment 4•18 years ago
|
||
Comment on attachment 250198 [details] [diff] [review]
patch
Avoid clicking stop while it's reloading ;-)
Attachment #250198 -
Flags: review?(neil) → review+
Assignee | ||
Updated•18 years ago
|
Whiteboard: [patch-r?] → [checkin needed]
Assignee | ||
Comment 5•18 years ago
|
||
mozilla/docshell/resources/content/netError.xhtml 1.17
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Whiteboard: [checkin needed]
I DON'T LIKE THIS DISABLED TRY AGAIN BUTTON!!!
I'm stuck on dialup too and get a lot of error pages too. However, I click the try again button on a few pages and can tell I have because the tab icon starts spinning. I can also tell when the try again reload is going to fail because in the status bar (it always happens this way for me) it says connecting to... BUT, if it says that for more than about 5-10 seconds, it will fail. Always. So I will click try again for a second time. However, now that the button is disabled I have to hit stop and try again. GRRRR about having to hit stop every time.
Also (and this is a bug I already filed: 410397) the blasted Try Again button is not re-enabled after hitting stop.
Travis
Assignee | ||
Comment 7•17 years ago
|
||
(In reply to comment #6)
> I DON'T LIKE THIS DISABLED TRY AGAIN BUTTON!!!
When I pointed you to this bug in bug 383729 comment 9 I wasn't doing it so that you could copy/paste your complaint into this bug. Perhaps you could try reading this bug's comment 0, and my bug 383729 comment 9 before mindlessly spamming the bug again.
Gavin, It seemed reasonable that I should re-post my complaint in the correct bug... I don't see how you consider that spam...? Also, I did read comment 0 on this bug, and thought another perspective, from another dialup user who DOES NOT AGREE WITH THIS, might be useful which is another reason I reposted the complaint along with information on how I know I've clicked the try again button and how I know a reload is going to fail before firefox times out on the page.
Also, if you bothered to read the post here, you would know I didn't _just_ copy and paste it, I edited it to add some additional information.
Assignee | ||
Comment 9•17 years ago
|
||
Travis: you're right, I overreacted. I was a little irritated yesterday for other reasons; I apologize for accusing you of spamming. I'm glad you filed bug 410397 - that was absolutely the right thing to do. It might have been best to put your arguments in that bug and just point to it from this one, however - not a big deal.
You need to log in
before you can comment on or make changes to this bug.
Description
•