Closed Bug 66898 Opened 24 years ago Closed 16 years ago

Startup status text needs polishing (active splash screen)

Categories

(Core :: XPCOM, enhancement)

enhancement
Not set
normal

Tracking

()

RESOLVED WONTFIX
mozilla1.5beta

People

(Reporter: mpt, Unassigned)

References

Details

(Keywords: polish)

Build: 2001010608, Mac OS 9.0 To reproduce: * Start Mozilla for the first time. (For the full effect, use a slow computer.) * Watch the splash screen. What you see: * `Starting up...' <http://lxr.mozilla.org/seamonkey/source/lib/mac/ MacMemoryAllocator/test/MemoryTest.cpp#47> * Several instances of `Registering native component {foo}' * Several instances of `Registering JS component {bar}' * `Component registration finished' <http://lxr.mozilla.org/seamonkey/source/xpcom/components/ nsComponentManager.cpp#2074> What you should see: * `Checking available memory...' * Several instances of `Registering native components ... {foo}' * Several instances of `Registering JS components ... {bar}' * `Starting up...' The last string is the most important of these -- since it is visible for considerably longer than any of the others, it would be more reassuring if it said `Starting up...' than if it said `Component registration finished'.
mpt: the "starting up..." text is in the dialog resource, and has nothing to do with memory checking. What's going on at that point is NS_InitXPCOM (reading the registry file etc). I agree we need better status text. After autoreg, we also need to show progress for reading default prefs, loading libraries etc.
Reassigning to default xpcom owner
Assignee: rayw → kandrot
reassigning kandrot bugs.
Assignee: kandrot → dougt
over to UI Design for suggestions.
Component: XPCOM Registry → User Interface Design
to default. assign back there is an idea of what strings should be displayed to the user.
Assignee: dougt → mpt
QA Contact: rayw → zach
Er, the default UI Design component assignee provided suggested strings in the original bug report. Back to XPCOM. :-) (The only change is that, given what Simon said, `Checking available memory...' should be `Looking for components...'.)
Assignee: mpt → dougt
Component: User Interface Design → XPCOM
Keywords: polish
QA Contact: zach → scc
I'm going to be working on this.
Assignee: dougt → sfraser
Summary: Startup status text needs polishing → Startup status text needs polishing (active splash screen)
Target Milestone: --- → mozilla0.9.8
0.9.9
Status: NEW → ASSIGNED
Target Milestone: mozilla0.9.8 → mozilla0.9.9
Depends on: 35866
Blocked by 35866, which is 1.0
Target Milestone: mozilla0.9.9 → mozilla1.0
Moving Netscape owned 0.9.9 and 1.0 bugs that don't have an nsbeta1, nsbeta1+, topembed, topembed+, Mozilla0.9.9+ or Mozilla1.0+ keyword. Please send any questions or feedback about this to adt@netscape.com. You can search for "Moving bugs not scheduled for a project" to quickly delete this bugmail.
Target Milestone: mozilla1.0 → mozilla1.2
I really believe Mozilla needs to have a splash screen with feedback on every OS. A splash screen with feedback will distract the user from the actual 'waiting for Mozilla to load' so that load times will feel shorter.
Target Milestone: mozilla1.2alpha → mozilla1.5alpha
Target Milestone: mozilla1.5alpha → mozilla1.5beta
This bug is targeted at a Mac classic platform/OS, which is no longer supported by mozilla.org. Please re-target it to another platform/OS if this bug applies there as well or resolve this bug. I will resolve this bug as WONTFIX in four weeks if no action has been taken. To filter this and similar messages out, please filter for "mac_cla_reorg".
Mac OS X no longer has a splash. Polish is required XP, on platforms that have a splash.
Assignee: sfraser → dougt
Status: ASSIGNED → NEW
OS: Mac System 8.5 → All
Hardware: Macintosh → All
Do any products show text any more?
Assignee: dougt → nobody
QA Contact: scc → xpcom
The splash screen isn't supported at all any more on the "new toolkit" platform that all Mozilla apps are using now, so we can't fix this.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.