It adds args to other port, userdir, headless and so on
Everything works. One little thing though. When I use --user-data-dir to specify a profile it get's overridden by one that seems to be hardcoded. Looks like it may be getting set wherever you're setting --remote-debugging-port=11752 and it looks like this:--user-data-dir="C:\Users\Work\AppData\Local\Temp\henqnzur.1jw" --bwsi
new ChromeDriverConfig { UserDir ="..", Headless = true, IsTempProfile = false, WindowSize = new WebSize(800, 600) }
set IsTempProfile = false, if true it delete dir when closing Chrome
Set ChromeProfilesWorker.ChromeBinaryFileName before opening Chrome. Must work
I'll check ChromeProfilesWorker.ChromeBinaryFileName later
Big architecture change committed today.
IAsyncWebBrowserClient moved to its own repository https://github.com/ToCSharp/IAsyncWebBrowserClient.
It is center point of my webbrowser projects.
Please, take a look. I value your opinion.
IAsyncWebBrowserClient moved to its own repository https://github.com/ToCSharp/IAsyncWebBrowserClient.
It is center point of my webbrowser projects.
Please, take a look. I value your opinion.
Update the nuget packages.
Write here any problems
Hello. I have made SeleniumAdapter.
Now we can run Unit Tests from Selenuim through SeleniumAdapter -> SyncWebDriver -> AsyncWebDriver -> AsyncChromeDriver
Now we can run Unit Tests from Selenuim through SeleniumAdapter -> SyncWebDriver -> AsyncWebDriver -> AsyncChromeDriver
Firefox 56 supports headless mode:
asyncFirefoxDriver = new AsyncFirefoxDriver(new FirefoxDriverConfig().SetHeadless().SetWindowSize(1200, 900));
webDriver = new WebDriver(asyncFirefoxDriver);
await webDriver.GoToUrl("https://www.bing.com/");
var screenshot = await webDriver.GetScreenshot();
using (MemoryStream imageStream = new MemoryStream(screenshot.AsByteArray))
{
System.Drawing.Image screenshotImage = System.Drawing.Image.FromStream(imageStream);
screenshotImage.Save(@"C:\temp\screenshot.png", System.Drawing.Imaging.ImageFormat.Png);
}
Working on asyncFirefoxDriver.OpenBrowserDevTools();
We can open Firefox developer tools with some limitations:
We can open Firefox developer tools with some limitations:
var profileName = tbOpenProfileName.Text;
asyncFirefoxDriver = new AsyncFirefoxDriver(
new FirefoxDriverConfig()
.SetProfileName(profileName)
.SetIsMultiprocessFalse()
.SetDoSetDebuggerRemoteEnabled());
webDriver = new WebDriver(asyncFirefoxDriver);
await webDriver.GoToUrl("https://www.google.com/");
await asyncFirefoxDriver.OpenBrowserDevTools();
// asyncFirefoxDriver.BrowserDevTools is AsyncFirefoxDriver
devToolsWebDriver = new WebDriver(asyncFirefoxDriver.BrowserDevTools);
//// TODO: not works SwitchTo().Frame("toolbox-iframe"); listener.js 1715
//await devToolsWebDriver.SwitchTo().Frame("toolbox-iframe");
//var inspectorTab = await devToolsWebDriver.FindElementById("toolbox-tab-inspector");
//await inspectorTab.Click();
DevTools not work in Multiprocess with content
Then we can debug Firefox developer tools itself:
await asyncFirefoxDriver.BrowserDevTools.OpenBrowserDevTools(9654);
FindElement methods improved:
await webDriver.Options().Timeouts.SetImplicitWait(TimeSpan.FromSeconds(3));
// name = "q", 0 - time to wait element, not use ImplicitWait
var prevQuery = await webDriver.FindElementByNameOrDefault("q", 0);
var res2 = await webDriver.GoToUrl("https://www.google.com/");
// if element with name "q" from prev page wait for new element with name "q"
var query = await webDriver.FindElementByName("q", prevQuery?.Id);
FindElementByNameOrDefault will not throw Exception if no element, return null
And use WebDriver, asyncChromeDriver.DevTools and Chrome native Developer Tools in parallel
AsyncChromeDriver opens WebSocket proxy for them
BrowsersDevToolsExample
Example of using Browser's Developer tools while using AsyncChromeDriver, AsyncOperaDriver and AsyncFirefoxDriver.
Example of using Browser's Developer tools while using AsyncChromeDriver, AsyncOperaDriver and AsyncFirefoxDriver.
Open Chrome native Developer tools for opened Chrome native Developer tools:
asyncChromeDriver = new AsyncChromeDriver(new ChromeDriverConfig().SetDoOpenBrowserDevTools());
asyncChromeDriver.BrowserDevToolsConfig = new ChromeDriverConfig().SetDoOpenBrowserDevTools();
webDriver = new WebDriver(asyncChromeDriver);
await asyncChromeDriver.Connect();
asyncChromeDriver.BrowserDevTools is AsyncChromeDriver, so we can interact with BrowserDevTools as AsyncWebDriver with some difficulties, because tabs behind shadowRoots. Look example :
var wd = new WebDriver(asyncChromeDriver.BrowserDevTools);
var el = await wd.ExecuteScript(shadowFind + "return recursiveFindById(document, 'tab-sources', [])[0];") as AsyncWebElement;
await el.Click();
Firefox BrowserDevTools also accessible, but here difficulties because they are in XUL:
await asyncFirefoxDriver.BrowserDevTools.JavaScriptExecutor
.ExecuteScript("frames[0].document.getElementById('toolbox-tab-netmonitor').click();");
Hi Oleg, I am using your AsyncChromeDriver to manage communications between a Windows desktop application and Chrome. As part of our workflow we send navigation requests to a web application via Chrome, we then use a custom Protocol ("afe") to send confirmations back to our desktop application. Chrome prompts us to enable the protocol and if the user checks the box Chrome updates the user's preference file, adding "afe":false the the protocol_handler section, so the following will appear "protocol_handler":{"excluded_schemes":{"afe": false}}. The browser session/process created by AsyncChromeDriver will create an empty "protocol_handler": "excluded_schemes" entry but doesn't add the "afe":false. Have you ever encountered this or is this a limitation of the Chrome DevTools? I would be very interested in any ideas/work-arounds you may know.
Here examples of opening Browsers: https://github.com/ToCSharp/AsyncWebDriver/tree/master/AllDriversExample
var profile = new ChromeDriverConfig()
{
UserDir = ProfilePath,// GetUserProfileDirectory().Result,
CommandLineArgumets = BuildStandardCommandLine()
};
_asyncChromeDriver = new AsyncChromeDriver(profile);
{
UserDir = ProfilePath,// GetUserProfileDirectory().Result,
CommandLineArgumets = BuildStandardCommandLine()
};
_asyncChromeDriver = new AsyncChromeDriver(profile);
_webDriver = new WebDriver(_asyncChromeDriver);
await _asyncChromeDriver.Connect();
Above is a code snippet that I use to initiate the connection to Chrome, I do not see the profile created until after the Connect method is called. There then seems to be a delay before I can access the profile.
What we are trying to do is create a profile by creating a Chrome instance using the above code. We then kill the Chrome process and update the preferences file using Json and then create a new instance of Chrome, that new instance should pick up the updated preferences. I have noticed that the preference file isn't always present.
https://github.com/ToCSharp/IAsyncWebBrowserClient/blob/master/IAsyncWebBrowserClient/BasicTypes/DriverConfig.cs
ChromeDriverConfig : DriverConfig
When you do: var profile = new ChromeDriverConfig()
{
UserDir = ProfilePath,// GetUserProfileDirectory().Result,
CommandLineArgumets = BuildStandardCommandLine()
};
IsTempProfile stays true, and it will delete this profile on close
new ChromeDriverConfig().SetUserDir(userDir) sets IsTempProfile = false;
ChromeDriverConfig : DriverConfig
When you do: var profile = new ChromeDriverConfig()
{
UserDir = ProfilePath,// GetUserProfileDirectory().Result,
CommandLineArgumets = BuildStandardCommandLine()
};
IsTempProfile stays true, and it will delete this profile on close
new ChromeDriverConfig().SetUserDir(userDir) sets IsTempProfile = false;
add profile.IsTempProfile = false
It gives us do some things before opening. For example look temp dir, driver wants to create