upgrade proposal to close the browser (headless or not):
you can add

ChromeTabPage>>>closeBrowser

	^self sendMessage: {
        'method' -> 'Browser.close'
      } asDictionary

#openForRemoteDebugging does self debugOn, but debugOn seems to be the default. Later there is 2 seconds wait without explanation. Why 2 seconds specifically?

There are 3 old legacy methods with GT inspector extensions.

Should be removed as we now do Spec2 which is more easy and allows to reuse the extension presenters

Hi,
When calling

browser closeAndExit.

a debug opens with an error : Does not understand #sigterm message

(i use the latest version with Pharo 11 and Pharo-OS-Windows)

i've a workaround in my environment... shall be generalized with Linux and MacOs version :

GoogleChrome>>>closeAndExit
	"Ask the browser to exit"

	chromeProcess ifNotNil: [ 
		chromeProcess process terminateProcessWithExitCode: 0.
		chromeProcess := nil ]

and:

Win32ChromePlatform>>>openChromeWith: arguments
 	
	| executableLocation cmd |
	executableLocation := '"',self defaultExecutableLocation,'"'.
	cmd := arguments ifEmpty: [ executableLocation ]
						 ifNotEmpty: [ executableLocation,' ',(self stringFromArguments: arguments) ].									
	
	^(self class environment at: #WinProcess) createProcess:  cmd.

It seems like NeoJSON would be a better choice. STON class mapping seems hardcoded for the use case of materializing previously-serialized Smalltalk objects

I'd like to evaluate javascript on a node e.g. (pseudocode) aNode.click() or aNode evaluate: 'click()'?

Hi and thanks for this project. I have been using it for the MiniDocs package, which extends documentation capabilities of Lepiter with light formats, including Mardeep preview and exportation.

A single line could be added to UnixChromePlatform class >>defaultExecutableLocations, so Pharo-Chrome would detect installations of Chromium in Unix, for those of us that prefer it over Chrome.

Thanks.