In the status line you display the following: Document: Done (0.332 secs) but sometimes its: Document: Done (0.33 secs) You have decide how many decimals that you're gonna show. Either it's 2 (0.33) or it's 4 (0.332) not sometimes 2 and sometimes 3. In the console it's always shown with 2 decimals.

This is handled in navigator.js. Over to XPApps/don ...

over to bill...

Fixing up bug properties

Could someone please check this in?

Yikes. It's always 3 decimals (it's just that sometimes the last one is a zero and displays as "" :-). I had higher priorities, but it is a trivial fix. Kind of a Catch-22, that. Shall we debate whether it should be hundredths or thousandths? Somebody's going to complain if they lose precision, I'm sure. Then I'll have a *real* bug on my hands.

blake or bill, could either one of you pls review henrik's patch and check it in? thx!

[whoops, pls pardon my last comment --i didn't get a collision with Bill, but didn't see his last comment posted either, till now.]

As far as an ordinary user is concerned, even one decimal place is stretching the bounds of usefulness. By all means show three decimal places in the Page Info dialog or wherever so that Web developers can check it, but for something which is shown in the status bar after every page load, two or more decimal places is really overkill. And while we're at it, can we take the opportunity to change `secs' to either `s' (the standards-compliant abbreviation:-) or `seconds'? Since we've got more than enough room to do so, I'd suggest using `seconds'.

nav triage team: Don't think we'll fix this for beta, though now might be a good time to get this patch in. Wink, wink, nudge, nudge. Marking nsbeta1-

is there any overall decision of how many decimals we should show?

Marking nsbeta1- bugs as future to get off the radar

This is invalid now that the status bar doesn't show the load time.