Closed Bug 127024 Opened 24 years ago Closed 24 years ago

[RFE] Full Screen mode needs a progress bar

Categories

(Core :: XUL, enhancement)

x86
All
enhancement
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 126720

People

(Reporter: ayo_adedipe, Assigned: hewitt)

Details

There needs to be some sort of implementation of a progress bar in Full screen mode so the user knows when a page is fully loaded. It doesn't need to be big. I suggest if they don't add status bar it should reside under the "minimuze, restore and close" buttons of the full screen window and it should be a little bar. If I had any coding abilities I would offer my help. If this can't be done at least the throbber should convulge or do whatever it does when a page is loading to be some type of indicator. I'm just writing this bug to inform you, but I know the Full Screen is still a work in progress. Keep up the good work and I'll keep up the rigorous testing.
I agree that a progress bar would be great, and I also like the idea of using the throbber for this, but a bar would also be good. It's true that the fullscreen mode is still in progress, but i like (and use more) the current implementation much better than the one some time ago, even if the current fullscreen mode gives me many visual glitches. Anyway, I'm confirming this bug, adding [RFE] in summary and changing severity to reflect the change.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Full Screen mode needs a progress bar → [RFE] Full Screen mode needs a progress bar
XP Toolkit/Widgets, --> hewitt. This could be closed as a dupe of bug 126720.
Assignee: asa → hewitt
Component: Browser-General → XP Toolkit/Widgets
QA Contact: doronr → jrgm
marking this a duplicate of 126720 because the solution to that bug is the same as this one - making important status bar items visible while in full screen. *** This bug has been marked as a duplicate of 126720 ***
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.