false positives from wasIdSeen method

[dh049]

when my ChatViewer instance is initializing, there seems to be nothing i can do to stop it from erroneously marking way too many messages as "read" when in reality they had flashed by as element are adjusting. is there something im missing to account for this? or could we use a new property that toggles the instance's ability to mark messages as "read"? or maybe a timeout value in milliseconds before a message is "read"?

[denysdovhan]

Any suggestions what API would be useful for you?
We don't currently use seen-methods, so we don't have a settled API yet. We would gladly receive suggestions from existing users.

I've made a draft PR for this #13. tldr: it marks items as seen by a delay. Only items that stayed for longer than seenDelayMs get into the seen ranges. I wonder if it'd fits your needs.

[dh049]

ya it sounds similar to my fix i have for now. currently im using chat-viewer to place my messages and scroll them and to constantly read whatever the current values of newestIndexInViewport and oldestIndexInViewport. from there i have applied some debouncing (sort of...) to whatever those values are to "see" the messages myself rather than using 'chat-viewer''s seen messages functionality. im also using that debounced value of oldestIndexInViewport to fetch more past messages whenever im at the top of the list rather than utilizing chat-viewer's onOlderMessages since that was firing off basically no matter what when the ChatViewer instance was initializing.

the reason i add "sort of..." to my debouncing is that its not exactly debouncing... i put a delay before coutning a message as being in the viewport, but no delay if the message then leaves the viewport, if that makes sense.