Closed wkeese closed 5 years ago
Could you provide a bit more environmental info? At least on macOS with Chrome 74, digdug 2.2.4, and leadfoot 2.2.10, maximize seems to be working.
Also, are the feature tests running, or is fixSessionCapabilities
set to false
or 'no-detect'
?
Oh, looks like it just got fixed. I was testing on macOS, leadfoot 2.2.9, DigDig 2.2.3, and Chrome 74. Just upgraded to Chrome 75, leadfoot 2.2.10, and DigDug 2.2.4, and now it's working!
(I guess those new versions of leadfoot and digdug are included in the new Intern you released 6 minutes ago.)
Just to answer your other question, I tried fixSessionCapabilities
both undefined (i.e. feature tests running), and no-detect
, but as I said above, I also tried explicitly setting usesWebDriverWindowCommands
.
The .maximizeWindow() command returns an error on Chrome:
Judging from https://w3c.github.io/webdriver/#maximize-window the command should be
window/maximize
rather thanwindow/current/maximize
So I tried explicitly settingusesWebDriverWindowCommands
to true:That makes Intern do a POST of
window/maximize
rather thanwindow/current/maximize
but Chrome doesn't like that either. It gets the same error: