Current we show progress for a single concept: loading. The throbber begins to throb when Firefox attempts to resolve the DNS of a link just clicked or entered, and stops when all resources have finished loading. We are looking at a variety of new designs for indicating progress, and many of them require us to differentiate between three states: stage 1) link clicked or entered, but server has not yet be located stage 2) first information recieved to first information drawn on the page stage 3) subsequent re-flows, until all content has finished loading This bug isn't about the UI but having the ability to design interfaces that involve two or three of these stages. For reference, I believe Chrome differentiates between (1) and (2/3) while Safari differentiates between (1/2) and (3). (At least I think so, it is worth looking more closely at their behaviors).
> For reference, I believe Chrome differentiates between (1) and (2/3) That's what we do now, too. This information was already available and just not used.