282980 2024-11-12 03:17:34 -0800 [WebDriver][BiDi] Implement log events buffering 2025-02-19 21:56:02 -0800 1 1 1 Unclassified WebKit WebDriver WebKit Nightly Build Unspecified Unspecified NEW InRadar P2 Normal --- 271956 288068 1 lmoura webkit-unassigned bburg webkit-bug-importer oldest_to_newest 2074478 0 lmoura 2024-11-12 03:17:34 -0800 https://w3c.github.io/webdriver-bidi/#module-log > A BiDi Session has a log event buffer which is a map from navigable id to a list of log events for that context that have not been emitted. User agents may impose a maximum size on this buffer, subject to the condition that if events A and B happen in the same context with A occurring before B, and both are added to the buffer, the entry for B must not be removed before the entry for A. From `log.entryAdded` event definition: https://w3c.github.io/webdriver-bidi/#event-log-entryAdded > 16. If event is enabled with session, "log.entryAdded" and related navigables, emit an event with session and body. > Otherwise, buffer a log event with session, related browsing contexts, and body. Storing events in buffer spec: https://w3c.github.io/webdriver-bidi/#buffer-a-log-event And in the end of `log.entryAdded` spec we have the definition of emitting these buffered events, which happen at the "remote end subscribe steps", with priority 10. That is, when the user subscribes to `log.entryAdded`, the remote end "flushes" the buffered events in order back to the client. 2076093 1 webkit-bug-importer 2024-11-19 03:18:27 -0800 <rdar://problem/140188887>