- From: Arvind Jain <arvind@google.com>
- Date: Wed, 7 May 2014 12:21:50 -0700
- To: Boris Zbarsky <bzbarsky@mit.edu>
- Cc: public-web-perf <public-web-perf@w3.org>
Received on Wednesday, 7 May 2014 19:22:18 UTC
We don't fire the event if the buffer is already full per step 20 of processing model. So your suggestion will be in conflict with that. given the user is explicitly reducing the size, it seems ok to not fire the event. On Wed, May 7, 2014 at 12:03 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote: > On 5/7/14, 2:58 PM, Arvind Jain wrote: > >> How about this text for section 4.4? Boris, does that address your >> concern? >> > > That's much better, yes. > > > 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. >> > > Perhaps "MUST NOT fire the resourcetimingbufferfull event until the next > attempt to add an element to the buffer"? > > -Boris >
Received on Wednesday, 7 May 2014 19:22:18 UTC