Re: [NavigationTiming] Uniqueness requirement for PerformanceTiming doesn't make much sense

    I think the intention was to distinguish PerformanceTiming objects
between different contexts. By now it doesn't
appear to have much meaning any more but confusion. I will remove it.

thanks,
Zhiheng

On Thu, Jun 28, 2012 at 10:10 AM, Jatinder Mann <jmann@microsoft.com> wrote:

> On Saturday, June 23, 2012 10:41 PM, Boris Zbarsky wrote:
> > The specification curently says (section 4.4):
> >
> >   Each browsing context must have a unique window.performance.timing
> >   attribute.
> >
> > Since browsing contexts outlive page loads, this means, on its face,
> that the
> > PerformanceTiming object is the same across pageloads in the same
> browsing context.
>
> I don't think this was the intention of the spec. Zhiheng, do you recall
> why you included that sentence? I recommend we remove it.
>
> Thanks,
> Jatinder
>
>
>