Re: [w3ctag/design-reviews] hasDroppedEntry in PerformanceObserverCallback (#547)

I like `wasEntryDropped`. If we want to imply potentially more than one, perhaps `wereEntriesDropped` could work as well.

If we want to remain specific to the current through the buffer (as opposed to other future causes), perhaps `wasBufferExceeded` or `wasLimitExceeded` could work as well. The benefit would be that it provides a strong signal about the event, and could be used to convey other side-effects as result of this. The downside, naturally, is that we could not use it when other causes may be introduced that may lead to entries being omitted.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/547#issuecomment-698540964