Alex Schwartz

> Extension Manager is now natively supported by GNOME 43 (and above). > > Let's use this issue to try and find a fix or workaround for older and current...

@mjakeman Haha nice, you will have to change the title of this issue again! https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/542101e8b51f55f2845ad6745e0b89ce7ce02196

Related: https://github.com/cypress-io/cypress/issues/28123 Definitely caused by the `browser.majorVersion` being equal to "for" ``` { name: 'chrome', family: 'chromium', channel: 'stable', displayName: 'Custom Chrome', version: 'for', path: 'PATH TO Chrome for Testing',...

``` const { defineConfig } = require("cypress"); module.exports = defineConfig({ e2e: { setupNodeEvents(on, config) { config.browsers.push({ name: 'cft', family: 'chromium', channel: 'stable', displayName: 'Custom Chrome', version: 'for', path: 'PATH TO...

Windows 10.0.19045.4170, Node.js v22.0.0 (same results on Command Prompt, Windows PowerShell, and Git Bash) ```sh PATH>node --run test -- A B [ 'NODE_22_PATH_TO_EXE', 'PATH\\script.js', "'A", "B'" ] (node:21628) ExperimentalWarning: Task...

I am only seeing this with `cypress open`, I don't see this with `cypress run` Does anyone see the same?

> I am only seeing this with `cypress open`, I don't see this with `cypress run` Nevermind.....I am now seeing this issue with `cypress run`

I updated the workaround here: https://github.com/cypress-io/cypress/issues/25891#issuecomment-1861098656

> Hi, I'd like to get some understanding on why this workaround doesn't work for people. To visit the correct URL to begin with. Is there a reason you need...

Lets say `test1` and `test2.com` are both in the host file and they go to the same IP Address and there is no https version cy.visit('http://test') - won't have the...