Group of 5 Under the hood
No documentation found
Plugins can now request keyboard focus and scroll position in their UI, plus use new clock.now/sleep/after/every timer functions
What
- New
ui.focusandui.scrollhook events let a plugin request or commit keyboard focus onto an element it drew, and move or reveal scroll position within a transcript or pane it owns, with ownership checks so one plugin can't steal focus or scroll from another plugin's UI, and tracking of whether a person or the plugin itself initiated the action. - The plugin-facing
$.uiobject gainsui.scroll(withto/in/blockoptions) andui.focus(withrequestId/key), plus newcloseOnEscape,holdToasts, androwsoptions onui.open. A third new event,ui.blit, was also registered in the event-type system. - A new
$.clockplugin API addsnow(),sleep(ms),after(ms, fn), andevery(ms, fn), each validated to require non-negative millisecond counts and wired through cancellation/abort signals.
Why These additions give plugins finer control over their own UI (focus and scrolling, without interfering with other plugins) and a built-in way to schedule timed or repeating work, instead of needing to work around the host for either.
Names in the bundleui.scrollui.focusui.blit
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubt
The finding does not say what a plugin or telemetry consumer can now build with these event types beyond their existence.