W3C home > Mailing lists > Public > public-web-perf@w3.org > March 2011

[NavigationTiming] .navigation and .timing

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Sun, 20 Mar 2011 13:06:14 +0200
Message-ID: <4D85DFA6.7020209@helsinki.fi>
To: public-web-perf@w3.org
Hi all,


I wonder why there is window.performance.timing (which is a very
generic name), and not just window.performance.navigation which could
contain all the information?

I assume window.performance itself is there so that we can add later new
features to it, like painting or something related to javascript handling.
But if we add window.performance.painting, window.performance.timing
has nothing to do with that, only with .navigation.
And that is strange.

If .navigation and .timing were merged, in the future we could end up
something like
interface Performance {
   readonly attribute PerformanceNavigation navigation;
   readonly attribute PerformanceScripting  scripting;
   readonly attribute PerformancePainting;  painting;
};
and all the attributes would have clearly distinct
meaning.





-Olli
Received on Sunday, 20 March 2011 11:06:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 20 March 2011 11:06:49 GMT