Hi @minhhd , Welcome to the forum. Could you share your test script? It looks like the website under test is trying to access an iframe from a different origin, and it might be best to resolve that issue. We do provide a workaround which should work if you add bypassCSP: true when creating a newContext: const context = browser.newContext({ bypassCSP: true Cheers, Ankur

However, am I correct in assuming that this code no longer works since k6 v0.46?

const context = browser.newContext({
  bypassCSP: true
From:
" * Browser options can now only be set using environment variables."
I searched for a relevant env variable but couldn’t fine one in the docs
Currently I get the following error
Blocked a frame with origin "https://mydomain.com" from accessing a cross-origin frame.
The code I’m attempting to execute is identical to the previous thread:
  console.log(page.evaluate(() => {
    return document.querySelector('iframe').contentWindow.document.getElementsByTagName('span')[0].innerText
              
Hello @colm3,
The code you provided remains functional in k6 v0.46. The bypassCSP setting belongs to the browserContext options, as outlined in the browserContext documentation, rather than being a browser module option. You can continue configuring it as you have before without necessitating the use of environment variables.
Kindly produce a test script that reproduces the issue, letting us offer assistance.
Thanks.
              
The “Blocked a frame with origin from accessing a cross-origin frame” error is triggered by the Same-Origin Policy in web browsers, which prevents scripts in one frame from directly accessing content in a frame from a different origin due to security concerns. To address this issue, you should employ cross-origin communication techniques such as postMessage() for controlled messaging between frames, configure Cross-Origin Resource Sharing (CORS) headers when controlling both source and destination servers, or use JSONP for data retrieval. Verify proper URL configuration, consider server-side solutions, and adhere to browser extension policies. These measures ensure secure and legitimate interactions between frames without violating the security constraints imposed by the Same-Origin Policy.
              
Hi @inancgumus
Here’s an example to reproduce the problem:

I’ve setup a tmp instance of a Braintree credit card form here:

https://k6csp.guruslabs.com/btree/
Here’s the sample k6 browser test I created