80556 - Definitive page load sizes.

Status: RESOLVED WONTFIX

(SeaMonkey :: Page Info, enhancement)

Description

[Sami Haahtinen]

The page info page could include extra information about the page such as, total
size including the images (just sum up the data that is there). Estimated
Loading times (size divided by speed).

And as other useful information (for which the data isn't there yet) parsing
errors and technologies used on the page (Javascript, Java, CSS, CSS2?)

Comment 1

[Fabian Guisset]

When you request enhancements, please file one bug per issue, for example one 
for the errors, one for the total size of the images, etc. There is a new Page 
Info dialog that is done and will be soon in Mozilla, but it doesn't have all 
the stuff you would like to see.
CC'ing Daniel and myself. Daniel should this be a dup?

Comment 2

[Daniel Brooks [:db48x]]

Good ideas. I was planning on image size already though. Dunno about dups, but a
dependancy will work just as well in this case.

Comment 3

[rob cherny]

hmmmm ... ok, so PLEASE forgive the spam ... is this the wrong place to ask for
added details in page info? ... I get impression it is ... 

basically i'd like to see something that lists the total page size, total images
size (including pre-loaded images), and the size of any and all linked files /
and types (.js, .css, .fla) etc ... 

Basically, give developers (for once) the definative page load size information.

A web browser seems to me the only place this can really definatively be nailed,
because, guess what, it just downloaded everything.

Anyway, as described here:

http://www.alistapart.com/discuss/read.cfm?forum=60&id=4256&thread=999

Nevermind the "Bandwidth Simulator" part of the posts ... just the info ... 

Let me know ... where should these info requests go ... ?

Adding cc too ... thanks.

Comment 4

[Jens-Uwe]

if the overall size should be used to find out download time, pictures which are
displayed more often should be only counted once.

Comment 5

[rob cherny]

of course.  please keep in mind also that in now way am i suggesting that 
mozilla estimate download times, only that it catalog / itemize all of a pages 
*unique* assets, and measure they're size.

Comment 6

[Markus Gerstel]

Referencing to Bug #88607 (stylesheet-tab)

I personally wish to see a "Size : xx kb" in the Page Info-dialog =)

Comment 7

[Benjamin Mucci]

Size should be there at less...

 

Comment 8

[Daniel Brooks [:db48x]]

changed the summary just so I can remeber what I'm supposed to do. Everything is
there except for the main total of html+images+stylesheets+etc (or at least will
be once bug 52730 is checked in.)

I think the most foolproof way to get the total size is not for the page info
window to add it up, but for everything to be added up as it's requested, and
then have Page Info just ask for it.

Comment 9

[Andy Edmonds]

Hmm, the add up as you get it approach sounds ok, but implementing bug 114446 
(.fileSize) would kill the 2 proverbial pterodactyls  and allow this to be 
computed in JS. 

Comment 10

[Boris 'pi' Piwinger]

*** Bug 139983 has been marked as a duplicate of this bug. ***

Comment 11

[Philip Chee]

Build identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.9.1b4pre) Gecko/20090422 SeaMonkey/2.0b1pre

Resolving as WORKSFORME. Since this bug was filed the PageInfo implementation has been totally rewritten. Please file new bugs against the new implementation for any remaining issues.

Comment 12

[Andrew Hagen]

I do not agree that RFEs should be automatically closed every time the underlying component is rewritten. 

This is a request for enhancement. It calls for information about total page size, including images. It calls for the information to be broken down. 

I don't necessarily see a need for this in our browsers, but it is an RFE. This is not WORKSFORME. 

If you need the information about total page sizes, etc, create a script using wget or curl. Users have no need for Seamonkey/Firefox to tell them the page size. As for page loading time, to do proper benchmarking you would have to use another program anyway. Putting in that statistic in our program would be generating useless, unreliable information. 

Changing coding to Resolved WONTFIX as this is unnecessary, and it will certainly never be implemented.