Navigation with iframe

[Crash--]

during recording session, if you go to a web page that loads iframe, we'll record all the navigation done by the iframes.

In some scenario, we'll want to follow iframe navigation but not in all cases, exemple:

• If I go on twake drive :
• top window === drive
• but I have an iframe with the data-proxy.
• If I click on record, I've at the end:

  - name: "Recording - qvalmori-dataproxy.twake.linagora.com"
version: "1.0.0"
description: "Auto-generated from recording"
steps:
  - action: navigate
    url: "https://qvalmori-dataproxy.twake.linagora.com/?intent=xxx"
  - action: navigate
    url: "https://qvalmori-dataproxy.twake.linagora.com/?intent=xxx"
  - action: click
    target:
      hints:
        - type: text_contains
          value: "adminis"
        - type: landmark_context
          value: "main"
  - action: click
    target:
      hints:
        - type: text_contains
          value: "adminis"
        - type: landmark_context
          value: "main"
  - action: click
    target:
      hints:
        - type: text_contains
          value: "adminis"
        - type: landmark_context
          value: "main"
  - action: click
    target:
      hints:
        - type: text_contains
          value: "creer"
        - type: class_contains
          value: "MuiButton-label"
        - type: landmark_context
          value: "complementary"

So if I replay the scenario it doesn't work, since the script goes to the dataproxy at first and then will never find the right (aka drive) content to interact with.

Perhaps the solution is to ignore iframe navigation as long as the URL does not interact with it. However, as soon as the user clicks on an iframe, we must track the navigation within it.

[mmaudet]

Hey @Crash-- , thanks for the report!

The issue comes from the content script being injected into all frames (allFrames: true) : iframe navigations (like your
data-proxy) were being captured as top-level navigate actions in the BSL script, which broke replay.

Fix applied (branch fix/iframe-navigation):

• Iframe navigations are now ignored at the source in NavigationCapture (window !== window.top)
• User interactions (click, input) inside iframes are also filtered out at the RecordingManager level to prevent orphaned
  actions in the script

The fix is intentionally minimal (2 guards, ~10 lines). Down the road we can add explicit iframe support in BSL (with a
frame field to scope actions), but for now everything from iframes is filtered out.

To test:

git fetch origin
git checkout fix/iframe-navigation
npm install && npm run build

Then load the extension (.output/chrome-mv3), go to Twake Drive, start a recording and verify that:

1. The generated BSL script no longer contains navigate actions pointing to data-proxy
2. Recorded actions correspond to interactions on the top window (Drive) only
3. Replay works as expected

Let me know if you hit any edge cases!