Ankur

@inancgumus I wasn't clear in the original description. The `dblclick` action in xk6-browser doesn't match the behaviour in playwright. Playwright script: ```js const { test, chromium } = require('@playwright/test'); test.describe('Editing',...

Interesting! I didn't come across this when I was running this locally. Instead I was facing the issue where `waitUntil: 'networkidle'` wasn't being handled correctly. The reason for that is...

> @imiric @ankur22 What do you think about calculating the offset vs. simply using the walltime field? Either of them are as good as each other since both solutions use...

> How frequently a local time on a cloud instance will change? I guess it will be super infrequent. So we can simply use the walltime field (without calculating the...

I like this approach. The issue is that we're going to be breaking everyone's script, and so this should probably be done asap (before the next release), just so that...

@inancgumus nice detailed write up. In the sync meeting it seemed that renaming the methods was the simpler approach. It felt like there were some unknowns with creating a new...

Is it possible to test this locally? I would've thought it was easier to find locally since it seems to rear its ugly head with lower latencies. I wonder if...

I'm going to describe the problem that we're having in the context of `xk6-browser`: 1. We can't guarantee that we can delete any temporary directories that we create, which is...

> For your particular case I would expect that you can workaround, as long as you don't need anything to be executed on the event loop - js code usually:...

page.waitForLoadState('networkidle') has been fixed in https://github.com/grafana/xk6-browser/pull/628.