Last Comment Bug 573385 - No busy indicator in fullscreen
: No busy indicator in fullscreen
Status: VERIFIED FIXED
fixed by bug 628654
: regression
Product: Firefox
Classification: Client Software
Component: General (show other bugs)
: unspecified
: All All
: -- enhancement with 1 vote (vote)
: Firefox 4.0b11
Assigned To: Nobody; OK to take it and work on it
:
:
Mentors:
Depends on: 482985 628654
Blocks: 481359
  Show dependency treegraph
 
Reported: 2010-06-20 13:27 PDT by Drew
Modified: 2011-05-20 05:25 PDT (History)
4 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Drew 2010-06-20 13:27:33 PDT
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3 GTB7.0
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.3) Gecko/20100423 Ubuntu/10.04 (lucid) Firefox/3.6.3 GTB7.0

This was reported for Ubuntu in Launchpad see: https://bugs.launchpad.net/bugs/596659

Below is a summary from the other report:
In full screen mode (F11), when clicking on URL and the new page is loading, there is no indication that the operation is in progress.

Reproducible: Always

Steps to Reproduce:
1. Open Firefox and press F11 to go fullscreen
2. Vist a website and click a link.
Actual Results:  
While loading, there is no indication that Firefox is making any progress.

Expected Results:  
A spinning cursor or other indication that Firefox is actively loading the new page.

This bug depends on Bug 482985 and Bug 171350.
Comment 1 Micah Gersten 2010-06-20 13:41:04 PDT
Accepting this so this functionality isn't forgotten.  This bug can be solved with either of those bugs.
Comment 2 Simona B [:simonab ] 2011-05-20 05:25:00 PDT
Mozilla/5.0 (Windows NT 5.1; rv:6.0a1) Gecko/20110519 Firefox/6.0a1

Verified issue using steps from Comment 0 on Ubuntu 10.10, WinXP, Mac OS X 10.6, Win 7. Loading of the page is now shown in the new "status bar".

Note You need to log in before you can comment on or make changes to this bug.