-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Synthetics Doesn’t Handle Popups (new tab or new window) #253
Comments
Needs this to be addressed - #287 |
@vigneshshanmugam with the latest version that includes these PRs, I can now see the correct screenshot in step 2, which is great!! On step 2, I still don't see any network traffic, is that what you'd expect with these updates, or is #287 still needed? |
@paulb-elastic Thanks for testing, We need this - #287 PR to be resolved to get the network traffic for these popups. |
@vigneshshanmugam I have tried this again, but still don't see the waterfall chart for step 2 (when step 2 is a popup page). Let me know if you want to catch up and go through it. |
For anyone following, this is working with inline monitors, so is likely to be an issue with my local glocal package build of Synthetics (as that will be used by Heartbeat, different to inline monitors) |
Reopening as result of this issue - #401 |
@vigneshshanmugam would you expect beta.18 or other changes (OS change) that have gone in, to fix this? I've tried with today's 8.0.0-SNAPSHOT, and, although I get the screenshot for the second step (the popup page), I get no waterfall chart. Are we still dependent on an update from Playwright and/or Chromium, or elsewhere? |
Not really, We need to follow the steps to fix this
|
The Synthetic Agent is capturing the performance data and screenshots for the main tab/page of the browser.
If a user journey causes a new tab or window (popup) to be opened, the metrics and screen shots are still taken from the initial (main) page, so there are no new metrics for the new tab/page, and the screenshot still reflects the original page.
This can be recreated by extending the todos folder/app
Create
./examples/todos/app/popup1.html
Create
./examples/todos/app/popup2.html
Create
./examples/todos/popup.journey.ts
Note that there are two test cases (both will fail in the same way)
We can act on the new/popup page, for example with
popup.waitForSelector
as shown in this example, however the Synthetic Agent is still connected to the CDP from the original window.When running this, you will notice:
The text was updated successfully, but these errors were encountered: