grafana/k6 · error

getting remote node %q: %w

Error message

getting remote node %q: %w

What it means

ContentFrame() runs CDP DOM.describeNode on the handle's remote object; this error wraps a protocol-level failure — typically an invalid/stale objectID ('Cannot find context element' style), a closed CDP session, or a dead target.

Source

Thrown at internal/js/modules/k6/browser/common/element_handle.go:859

		&opts.ElementHandleBasePointerOptions,
	)
	if _, err := call(h.ctx, click, opts.Timeout); err != nil {
		return fmt.Errorf("clicking on element: %w", err)
	}
	applySlowMo(h.ctx)

	return nil
}

// ContentFrame returns the frame that contains this element.
func (h *ElementHandle) ContentFrame() (*Frame, error) {
	var (
		node *cdp.Node
		err  error
	)
	action := dom.DescribeNode().WithObjectID(h.remoteObject.ObjectID)
	if node, err = action.Do(cdp.WithExecutor(h.ctx, h.session)); err != nil {
		return nil, fmt.Errorf("getting remote node %q: %w", h.remoteObject.ObjectID, err)
	}
	if node == nil || node.FrameID == "" {
		return nil, fmt.Errorf("element is not an iframe")
	}

	frame, ok := h.frame.manager.getFrameByID(node.FrameID)
	if !ok {
		return nil, fmt.Errorf("frame not found for id %s", node.FrameID)
	}

	return frame, nil
}

// Dblclick scrolls element into view and double clicks on the element.
func (h *ElementHandle) Dblclick(opts *ElementHandleDblclickOptions) error {
	dblclick := func(_ context.Context, handle *ElementHandle, p *Position) (any, error) {
		return nil, handle.dblclick(p, opts.ToMouseClickOptions())
	}

View on GitHub (pinned to 93accf6570)

Solutions

1. Re-query the element and call contentFrame() immediately after locating it
2. Avoid caching handles across navigations; re-resolve per action
3. Check browser/session health if the wrapped error mentions closed targets
4. Increase the surrounding timeout so iframe attachment completes first

Example fix

// before
await storedHandle.contentFrame(); // getting remote node: ... 

// after
const iframeEl = await page.$('#myframe');
const frame = await iframeEl.contentFrame();

try {
  const frame = await handle.contentFrame();
} catch (e) {
  if (String(e).includes('getting remote node')) {
    handle = await page.$(sel); // fresh objectID
    return await handle.contentFrame();
  }
  throw e;
}

When it happens

Trigger: handle.contentFrame() (or frame-crossing selector resolution reaching it) on a handle whose node was removed, after navigation invalidated objectIDs, or when the browser session/target died.

Common situations: ElementHandles stored across navigations; out-of-process iframe teardown races; browser crash/OOM; slow pages where the handle outlives its context.

Related errors

• getting iframe frame: %w
• getting bounding box: %w
• no frame found for node: %w
• expected node but got %s
• getting frame owner: %w

AI-assisted analysis of grafana/k6@93accf6570 (2026-08-15). Data as JSON: /api/errors/5d86bf90cd4ca06d. Report an issue: GitHub.