- From: Arvind Jain <arvind@google.com>
- Date: Wed, 7 May 2014 11:58:20 -0700
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: public-web-perf <public-web-perf@w3.org>
- Message-ID: <CAOYaDdPS=cVBpxriYO+SuutqDUhONg7fn=HaQpYWEHGbVm0dfg@mail.gmail.com>
How about this text for section 4.4? Boris, does that address your concern? Arvind setResourceTimingBufferSize method The setResourceTimingBufferSize method, when invoked, must set the maximum number of PerformanceResourceTiming<http://www.w3.org/TR/resource-timing/#performanceresourcetiming> resources that may be stored in the buffer to the value of the maxSize parameter. The buffer is considered to be full if the number of entries in it is greater than or equal to maxSize. If this method is not called, the user agent should store at least 150 PerformanceResourceTiming<http://www.w3.org/TR/resource-timing/#performanceresourcetiming> resources in the buffer, unless otherwise specified by the user agent. If the maxSize parameter is less than the number of elements currently stored in the buffer, no elements in the buffer are to be removed. In this case, the user agent MUST not fire the resourcetimingbufferfull event. On Wed, May 7, 2014 at 10:47 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 5/7/14, 1:40 PM, Arvind Jain wrote: > >> Please let me know if the change I suggested above will address your >> concerns. >> > > It doesn't completely address mine, since there is still no definition of > what it means for the buffer to be full. I would like the spec to actually > spell that out clearly. > > -Boris >
Received on Wednesday, 7 May 2014 18:58:48 UTC