In the Recorder Fails to Launch on Chrome 137, Katalon wrote
Root Cause
Chrome 137 introduces internal changes that prevent the Katalon Studio Web Recorder from initiating browser control via standard automation protocols. As a result, the built-in recorder fails to launch when Chrome 137 is used as the execution environment.
This sentence does not explain the technical reason clearly.
Just adding an external reference:
Remove --load-extension command line switch back to top
To enhance the security and stability of the Chrome browser for our users, official Chrome branded builds will begin to deprecate the ability to load extensions using the--load-extensioncommand-line flag, starting in Chrome 137. This change aims to mitigate the risks associated with harmful and unwanted extensions.
Unpacked extensions can be loaded with the Load unpacked button on the Extensions management page (chrome://extensions/) with Developer mode enabled.
Developers can still use the--load-extensionswitch in non-branded builds such as Chromium and Chrome For Testing.
Chrome 137 on ChromeOS, Linux, macOS, Windows
There seems to be a good reason that
- Katalon Studio can no longer work with Chrome (branded) 137 and newer
- Katalon Studio can only work with Chrome for Testing
Am I right?
To me, this change look very significant.