Re: Resource Timing

On Tue, Aug 24, 2010 at 12:32 PM, Bryan McQuade <bmcquade@google.com> wrote:

> Interesting. Can you expand on the meta header approach?
>

   Some initial thought according to the feedbacks so far: ResourceTiming
will be available
for resources on the same origin only, unless a specific html header exists.
The header contains
info about which domain(s) are allowed to access the ResourceTiming of this
resource.



> I assume you are referring to a case where a child iframe is on a
> different origin. In that case it would not be appropriate to leak the
> timing info for the frame up to the parent. But it sounds like this
> meta header might allow the child frame to give permission to leak the
> info to the parent?
>

    yes.

    A previous solution is to remove most of the detail timings from
ResourceTiming
by keeping only the starting time and the onload time. But then the proposal
loses much
of its value.

cheers,
Zhiheng


> On Tue, Aug 24, 2010 at 12:49 PM, Zhiheng Wang <zhihengw@google.com>
> wrote:
> >     The immediate questions for ResourceTiming is how to maintain privacy
> > while exposing those timing information.
> > So far using meta header on top of the same origin policy seems to be the
> > way to start. An update should be available
> > later this week.
> > cheers,
> > Zhiheng
> >
> >
> > On Mon, Aug 23, 2010 at 12:41 PM, Jason Sobel <jsobel@facebook.com>
> wrote:
> >>
> >> Hey all-
> >>
> >> Looks like you're making great progress on navigation timing -- very
> >> exciting!
> >>
> >>
> >>
> >> Do you have any thoughts on polishing and implementing resource timing?
> >> That data is very interesting to us at Facebook so I'm hoping it will be
> >> available in all the major browsers sooner rather than later.
> >>
> >>
> >>
> >> Thanks much!
> >>
> >>
> >>
> >>               --jason
> >>
> >>
> >
>