George S. Baugh

Oh - One more thing: If you just want to chat, I have a matrix server. https://chat.troglodyne.net/ The "Troglodyne Open Source Support" public channel there would probably be where to...

Not yet. That said it's probably pretty easy to add, given I support it in Selenium::Client already. I'll make a subclass of Selenium::Chrome to make it work tomorrow. Thanks for...

1. I don't see why not, that's what I use with Selenium::Client. 2. the subclass I make should handle the extra_capabilities such that you don't have to even pass them....

ah, I understand now. The special capabilities name for edge is: `ms:EdgeOptions`

example of capabilities for edge to start headless: ``` my $caps = { AlwaysMatch => { browser => 'MicrosoftEdge', ms:EdgeOptions => { args => ['-headless'], } } } # This...

Updated Selenium::Edge in b92685715ff5a0b9433a09157fbef37b5d1a0c5f

Selenium::Client is my new selenium module, yes. S::R::D is a big huge pain to maintain. It also doesn't support Selenium 4.0 ... which won't be a problem for you if...

Any selenium client can use selenium servers, such as the java based one from SeleniumHQ ("the jar file"). Selenium::Client is capable of using the newest version of SeleniumHQ's server. Selenium::Remote::Driver...

Examples of the difference illustrated: ``` # Spawn instance of every browser with S::R::D my @browsers = qw{Firefox Chrome Edge}; my @drivers_srd = map { "Selenium::$_"->new() } @browsers; my @drivers_sc...

Aside from all those base features, the other primary difference is that the selenium method names themselves are different. S::R::D's method names all correspond to the JSONWire selenium method names,...