Re: Implementing the web timing spec

    Enabling the interface, through HTTP header etc, sounds like a
good idea at this time.
For the root document though, it's already too late to populate some
attributes (DNS, etc).
So how about enabling the timing for the root document all the time
but making the element timing
configurable? The overhead of keeping the root document timings should
be rather minimal.

thanks,
Zhiheng

On Mar 7, 5:05 am, Georg Maaß <[email protected]> wrote:
> johnjbarton wrote:
> > That places a burden on all users for performance timing information
> > useful to a few. Should we adopt this broadly and put more profiling and
> > debugging into DOM? If not why this particular one?
>
> I think we should make it configurable whether to enable it by default,
> if the website requests for it, whether to ask the user, if the web site
> requests for it, or whether to always keep it of. I think we should not
> switch it on, if the website does not request for it using a HTTP
> header, which is to be specified.
>
> For non HTTP sources other rules might be specified, when to enable it.
> Default should be not to enable it to prevent that burdon on each user
> even those not using int.