Skip to content

fix: support cross-origin iframe snapshots#1048

Open
Zqian007 wants to merge 1 commit intovercel-labs:mainfrom
Zqian007:fix-cross-iframe
Open

fix: support cross-origin iframe snapshots#1048
Zqian007 wants to merge 1 commit intovercel-labs:mainfrom
Zqian007:fix-cross-iframe

Conversation

@Zqian007
Copy link
Copy Markdown

Proactively attach to untracked iframe targets via Target.getTargets
before taking a snapshot, ensuring cross-origin iframes that were
missed during Target.attachedToTarget events are captured.

In snapshot.rs, fall back to dedicated iframe sessions for cross-origin
iframes when resolve_iframe_frame_id fails due to same-origin policy,
instead of silently skipping them.

@vercel
Copy link
Copy Markdown
Contributor

vercel bot commented Mar 27, 2026

Someone is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

…n TCP bind (vercel-labs#1041)

On Windows the daemon derives a TCP port from the session name via a
djb2 hash (e.g. "default" → 50838). On many machines this port falls
inside Hyper-V's excluded port range (winnat), causing EACCES on bind
and preventing the daemon from starting.

Changes:
- daemon: try the hash-derived port first; on failure, bind to port 0
  (OS-assigned) and write the actual port to the .port file
- client (connection.rs, stream.rs): read the .port file to discover the
  daemon's actual port, falling back to the hash if the file is absent
- run_daemon: guard .sock file operations with #[cfg(unix)] and add
  .port file cleanup for #[cfg(windows)]

Fixes vercel-labs#390

Co-authored-by: ctate <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants