From 7dfecd94d673faecf5c5e6e20700e3f73d3df562 Mon Sep 17 00:00:00 2001 From: wbamberg Date: Mon, 13 May 2024 17:02:11 -0700 Subject: [PATCH] Update files/en-us/web/api/performanceobserver/performanceobserver/index.md Co-authored-by: Barry Pollard --- .../web/api/performanceobserver/performanceobserver/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/files/en-us/web/api/performanceobserver/performanceobserver/index.md b/files/en-us/web/api/performanceobserver/performanceobserver/index.md index d7c42972bef8565..795c29780d6faaf 100644 --- a/files/en-us/web/api/performanceobserver/performanceobserver/index.md +++ b/files/en-us/web/api/performanceobserver/performanceobserver/index.md @@ -65,7 +65,7 @@ observer.observe({ entryTypes: ["measure", "mark"] }); ### Dropped buffer entries You can use {{domxref("PerformanceObserver")}} with a `buffered` flag to listen to past performance entries. -There is a buffer size limit, though. The performance observer callback contains an `options` object: the first time the observer calls the callback, the `options` parameter will have a `droppedEntriesCount` property that tells you how many entries were dropped due to the buffer storage being full. +There is a buffer size limit, though. The performance observer callback contains an `options` object: the first time the observer calls the callback, the `options` parameter will have a `droppedEntriesCount` property that tells you how many entries were dropped due to the buffer storage being full. Subsequent callbacks will have an empty `options` parameter. ```js function perfObserver(list, observer, options) {