update google sdk for gemini. Better frame context cleanup - #68
Conversation
There was a problem hiding this comment.
Bug: Cross-origin frame processing accidentally removed from loop
The collectCrossOriginFrameData call and processedCrossOriginFrames.add(frameId) were removed from the cross-origin frame branch, but the conditional structure was left intact. Now when isCrossOrigin && frameId && session is true and the frame hasn't been processed, the code falls through without doing anything. The processedCrossOriginFrames.has(frameId) check at line 474 will always be false since nothing populates the set in this loop anymore. While OOPIF processing later handles frames from frameContextManager.getOOPIFs(), any cross-origin frames discovered in maps.frameMap that aren't tracked as OOPIFs will be silently skipped.
src/context-providers/a11y-dom/index.ts#L472-L479
HyperAgent/src/context-providers/a11y-dom/index.ts
Lines 472 to 479 in cef2693
Note
Parallelizes OOPIF processing via FrameContextManager, adds thorough frame cleanup on detach, and updates @google/genai to 1.30.0.
removeFramecleanup: clears execution contexts, waiters, OOPIF session listeners, and OOPIF tracking before removing from graph/sessions.removeFrame).FrameContextManager.getOOPIFs()andcollectCrossOriginFrameData, merging results into shared maps.waitForExecutionContextand session annotation.@google/genaito^1.30.0and bump package version to1.0.6.Written by Cursor Bugbot for commit cef2693. This will update automatically on new commits. Configure here.