Morph MORPH
SIGN IN SIGN UP
cefsharp / CefSharp UNCLAIMED

.NET (WPF and Windows Forms) bindings for the Chromium Embedded Framework

0 0 1 C#
Normal View History Raw
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
// Copyright © 2017 The CefSharp Authors. All rights reserved.
//
// Use of this source code is governed by a BSD-style license that can be found in the LICENSE file.
Test - Add expiry to DevToolsClientFacts.CanSetCookieForDomain test #3218
2020-10-16 19:57:43 +10:00
using System;
DevTools Client - Serialize lists of DevToolsDomainEntityBase (#3487)
2021-04-08 21:38:15 +02:00
using System.Collections.Generic;
Test - Add DevToolsClientFacts.CanCaptureScreenshot - Capture screenshot, load data and confirm width/height match browser
2021-06-21 10:25:56 +10:00
using System.Drawing;
using System.Drawing.Imaging;
using System.IO;
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
using System.Threading.Tasks;
DevTools Client - Generic ExecuteDevToolsMethodAsync and add RegisterEventHandler (#3674) * Make ExecuteDevToolsMethodAsync generic * Make RegisterEventHandler generic * PR feedback and added test for registering multiple event handlers * Updated generated code to latest version * Fix possible NRE when removing event listener before adding one
2021-07-26 04:01:46 +02:00
using CefSharp.DevTools;
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
using CefSharp.DevTools.Browser;
DevTools Client - Serialize lists of DevToolsDomainEntityBase (#3487)
2021-04-08 21:38:15 +02:00
using CefSharp.DevTools.Emulation;
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
using CefSharp.DevTools.Network;
using CefSharp.Example;
using CefSharp.OffScreen;
using Xunit;
using Xunit.Abstractions;
namespace CefSharp.Test.DevTools
{
//NOTE: All Test classes must be part of this collection as it manages the Cef Initialize/Shutdown lifecycle
[Collection(CefSharpFixtureCollection.Key)]
Test - Code Cleanup - Start splitting tests out into own files where relevant - Improve call ordering - Use Assert.RaisesAsync where possible - Classes have been renamed (Tests is now the standard suffix) TODO: Some of the classes still need their method names changed
2023-02-15 13:45:07 +10:00
public class DevToolsClientTests
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
{
private readonly ITestOutputHelper output;
private readonly CefSharpFixture fixture;
Test - Code Cleanup - Start splitting tests out into own files where relevant - Improve call ordering - Use Assert.RaisesAsync where possible - Classes have been renamed (Tests is now the standard suffix) TODO: Some of the classes still need their method names changed
2023-02-15 13:45:07 +10:00
public DevToolsClientTests(ITestOutputHelper output, CefSharpFixture fixture)
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
{
this.fixture = fixture;
this.output = output;
}
Test - Add DevToolsClientFacts.CanCaptureScreenshot - Capture screenshot, load data and confirm width/height match browser
2021-06-21 10:25:56 +10:00
[Fact]
public async Task CanCaptureScreenshot()
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("www.google.com", useLegacyRenderHandler: false))
Test - Add DevToolsClientFacts.CanCaptureScreenshot - Capture screenshot, load data and confirm width/height match browser
2021-06-21 10:25:56 +10:00
{
Core - Rename WaitForBrowserInitialLoadAsync to WaitForInitialLoadAsync and simplify - Initial intention was to have a reusable method that could be used CefSharp.Wpf.HwndHost, upon further deliberation I've decided to build the functionality into the ChromiumWebBrowser.Partial.cs and will need to duplicate the functionality in CefSharp.Wpf.HwndHost. This guarantees that the Task will be resolved in all cases. The previous implementation there was a theoretical change we'd miss subscribing to the relevant events - Remove CancellationToken as it's not possible to cancel Issue #3842
2021-10-28 10:30:03 +10:00
await browser.WaitForInitialLoadAsync();
Test - Add DevToolsClientFacts.CanCaptureScreenshot - Capture screenshot, load data and confirm width/height match browser
2021-06-21 10:25:56 +10:00
using (var devToolsClient = browser.GetDevToolsClient())
{
var response = await devToolsClient.Page.CaptureScreenshotAsync();
Assert.NotNull(response.Data);
Test - Minor cleanup
2021-07-05 11:16:25 +10:00
Assert.NotEmpty(response.Data);
Test - Add DevToolsClientFacts.CanCaptureScreenshot - Capture screenshot, load data and confirm width/height match browser
2021-06-21 10:25:56 +10:00
var image = Image.FromStream(new MemoryStream(response.Data));
var size = browser.Size;
Assert.NotNull(image);
Assert.Equal(ImageFormat.Png, image.RawFormat);
Assert.Equal(size.Width, image.Width);
Assert.Equal(size.Height, image.Height);
}
}
}
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
[Fact]
public void CanConvertDevToolsObjectToDictionary()
{
var bounds = new Bounds
{
Height = 1,
Width = 1,
Left = 1,
Top = 1,
WindowState = WindowState.Fullscreen
};
var dict = bounds.ToDictionary();
Assert.Equal(bounds.Height, (int)dict["height"]);
Assert.Equal(bounds.Width, (int)dict["width"]);
Assert.Equal(bounds.Top, (int)dict["top"]);
Assert.Equal(bounds.Left, (int)dict["left"]);
Assert.Equal("fullscreen", (string)dict["windowState"]);
}
[Fact]
public async Task CanGetDevToolsProtocolVersion()
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("www.google.com", useLegacyRenderHandler: false))
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
{
Core - Rename WaitForBrowserInitialLoadAsync to WaitForInitialLoadAsync and simplify - Initial intention was to have a reusable method that could be used CefSharp.Wpf.HwndHost, upon further deliberation I've decided to build the functionality into the ChromiumWebBrowser.Partial.cs and will need to duplicate the functionality in CefSharp.Wpf.HwndHost. This guarantees that the Task will be resolved in all cases. The previous implementation there was a theoretical change we'd miss subscribing to the relevant events - Remove CancellationToken as it's not possible to cancel Issue #3842
2021-10-28 10:30:03 +10:00
await browser.WaitForInitialLoadAsync();
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
using (var devToolsClient = browser.GetDevToolsClient())
{
var response = await devToolsClient.Browser.GetVersionAsync();
var jsVersion = response.JsVersion;
var revision = response.Revision;
Assert.NotNull(jsVersion);
Assert.NotNull(revision);
output.WriteLine("DevTools Revision {0}", revision);
}
}
}
[Fact]
DevTools Client - Make Message Id globally unique When attempting to use two DevTools Client instances the message Id fails validation as it's not incrementing per CefBrowser instance. This should be made unique per CefBrowser Issue #3341 has been created to document improving this.
2021-01-08 17:03:24 +10:00
public async Task CanEmulationCanEmulate()
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("www.google.com", useLegacyRenderHandler: false))
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
{
Core - Rename WaitForBrowserInitialLoadAsync to WaitForInitialLoadAsync and simplify - Initial intention was to have a reusable method that could be used CefSharp.Wpf.HwndHost, upon further deliberation I've decided to build the functionality into the ChromiumWebBrowser.Partial.cs and will need to duplicate the functionality in CefSharp.Wpf.HwndHost. This guarantees that the Task will be resolved in all cases. The previous implementation there was a theoretical change we'd miss subscribing to the relevant events - Remove CancellationToken as it's not possible to cancel Issue #3842
2021-10-28 10:30:03 +10:00
await browser.WaitForInitialLoadAsync();
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
using (var devToolsClient = browser.GetDevToolsClient())
{
var response = await devToolsClient.Emulation.CanEmulateAsync();
Assert.True(response.Result);
}
}
}
[Fact]
public async Task CanGetPageNavigationHistory()
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("www.google.com", useLegacyRenderHandler: false))
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
{
Core - Rename WaitForBrowserInitialLoadAsync to WaitForInitialLoadAsync and simplify - Initial intention was to have a reusable method that could be used CefSharp.Wpf.HwndHost, upon further deliberation I've decided to build the functionality into the ChromiumWebBrowser.Partial.cs and will need to duplicate the functionality in CefSharp.Wpf.HwndHost. This guarantees that the Task will be resolved in all cases. The previous implementation there was a theoretical change we'd miss subscribing to the relevant events - Remove CancellationToken as it's not possible to cancel Issue #3842
2021-10-28 10:30:03 +10:00
await browser.WaitForInitialLoadAsync();
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
using (var devToolsClient = browser.GetDevToolsClient())
{
var response = await devToolsClient.Page.GetNavigationHistoryAsync();
var currentIndex = response.CurrentIndex;
var entries = response.Entries;
Assert.Equal(0, currentIndex);
Assert.NotNull(entries);
Assert.True(entries.Count > 0);
Assert.Equal(CefSharp.DevTools.Page.TransitionType.Typed, entries[0].TransitionType);
}
}
}
[Theory]
//[InlineData("CefSharpTest", "CefSharp Test Cookie", CefExample.ExampleDomain, CookieSameSite.None)]
[InlineData("CefSharpTest1", "CefSharp Test Cookie2", CefExample.ExampleDomain, CookieSameSite.Lax)]
public async Task CanSetCookieForDomain(string name, string value, string domain, CookieSameSite sameSite)
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("www.google.com", useLegacyRenderHandler: false))
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
{
Core - Rename WaitForBrowserInitialLoadAsync to WaitForInitialLoadAsync and simplify - Initial intention was to have a reusable method that could be used CefSharp.Wpf.HwndHost, upon further deliberation I've decided to build the functionality into the ChromiumWebBrowser.Partial.cs and will need to duplicate the functionality in CefSharp.Wpf.HwndHost. This guarantees that the Task will be resolved in all cases. The previous implementation there was a theoretical change we'd miss subscribing to the relevant events - Remove CancellationToken as it's not possible to cancel Issue #3842
2021-10-28 10:30:03 +10:00
await browser.WaitForInitialLoadAsync();
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
using (var devToolsClient = browser.GetDevToolsClient())
{
Test - Add expiry to DevToolsClientFacts.CanSetCookieForDomain test #3218
2020-10-16 19:57:43 +10:00
var expiry = DateTimeOffset.UtcNow.AddDays(10);
var response = await devToolsClient.Network.SetCookieAsync(name, value, domain: domain, sameSite: sameSite, expires: expiry.ToUnixTimeSeconds());
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
Assert.True(response.Success, "SetCookieForDomain");
}
}
}
DevTools Client - Make Message Id globally unique When attempting to use two DevTools Client instances the message Id fails validation as it's not incrementing per CefBrowser instance. This should be made unique per CefBrowser Issue #3341 has been created to document improving this.
2021-01-08 17:03:24 +10:00
[Fact]
public async Task CanUseMultipleDevToolsClientInstancesPerBrowser()
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("www.google.com", useLegacyRenderHandler: false))
DevTools Client - Make Message Id globally unique When attempting to use two DevTools Client instances the message Id fails validation as it's not incrementing per CefBrowser instance. This should be made unique per CefBrowser Issue #3341 has been created to document improving this.
2021-01-08 17:03:24 +10:00
{
Core - Rename WaitForBrowserInitialLoadAsync to WaitForInitialLoadAsync and simplify - Initial intention was to have a reusable method that could be used CefSharp.Wpf.HwndHost, upon further deliberation I've decided to build the functionality into the ChromiumWebBrowser.Partial.cs and will need to duplicate the functionality in CefSharp.Wpf.HwndHost. This guarantees that the Task will be resolved in all cases. The previous implementation there was a theoretical change we'd miss subscribing to the relevant events - Remove CancellationToken as it's not possible to cancel Issue #3842
2021-10-28 10:30:03 +10:00
await browser.WaitForInitialLoadAsync();
DevTools Client - Make Message Id globally unique When attempting to use two DevTools Client instances the message Id fails validation as it's not incrementing per CefBrowser instance. This should be made unique per CefBrowser Issue #3341 has been created to document improving this.
2021-01-08 17:03:24 +10:00
using (var devToolsClient = browser.GetDevToolsClient())
{
var response = await devToolsClient.Browser.GetVersionAsync();
var jsVersion = response.JsVersion;
var revision = response.Revision;
Assert.NotNull(jsVersion);
Assert.NotNull(revision);
output.WriteLine("DevTools Revision {0}", revision);
}
using (var devToolsClient = browser.GetDevToolsClient())
{
var response = await devToolsClient.Browser.GetVersionAsync();
var jsVersion = response.JsVersion;
var revision = response.Revision;
Assert.NotNull(jsVersion);
Assert.NotNull(revision);
output.WriteLine("DevTools Revision {0}", revision);
}
}
}
DevTools Client - Serialize lists of DevToolsDomainEntityBase (#3487)
2021-04-08 21:38:15 +02:00
[Fact]
public async Task CanSetUserAgentOverride()
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("www.google.com", useLegacyRenderHandler: false))
DevTools Client - Serialize lists of DevToolsDomainEntityBase (#3487)
2021-04-08 21:38:15 +02:00
{
Core - Rename WaitForBrowserInitialLoadAsync to WaitForInitialLoadAsync and simplify - Initial intention was to have a reusable method that could be used CefSharp.Wpf.HwndHost, upon further deliberation I've decided to build the functionality into the ChromiumWebBrowser.Partial.cs and will need to duplicate the functionality in CefSharp.Wpf.HwndHost. This guarantees that the Task will be resolved in all cases. The previous implementation there was a theoretical change we'd miss subscribing to the relevant events - Remove CancellationToken as it's not possible to cancel Issue #3842
2021-10-28 10:30:03 +10:00
await browser.WaitForInitialLoadAsync();
DevTools Client - Serialize lists of DevToolsDomainEntityBase (#3487)
2021-04-08 21:38:15 +02:00
using (var devToolsClient = browser.GetDevToolsClient())
{
var brandsList = new List<UserAgentBrandVersion>();
Test - Minor cleanup
2021-07-05 11:16:25 +10:00
var uab = new UserAgentBrandVersion
{
Brand = "Google Chrome",
Version = "89"
};
DevTools Client - Serialize lists of DevToolsDomainEntityBase (#3487)
2021-04-08 21:38:15 +02:00
brandsList.Add(uab);
Test - Minor cleanup
2021-07-05 11:16:25 +10:00
var uab2 = new UserAgentBrandVersion
{
Brand = "Chromium",
Version = "89"
};
DevTools Client - Serialize lists of DevToolsDomainEntityBase (#3487)
2021-04-08 21:38:15 +02:00
brandsList.Add(uab2);
Test - Minor cleanup
2021-07-05 11:16:25 +10:00
var ua = new UserAgentMetadata
{
Brands = brandsList,
Architecture = "arm",
Model = "Nexus 7",
Platform = "Android",
PlatformVersion = "6.0.1",
FullVersion = "89.0.4389.114",
Mobile = true
};
DevTools Client - Serialize lists of DevToolsDomainEntityBase (#3487)
2021-04-08 21:38:15 +02:00
await devToolsClient.Emulation.SetUserAgentOverrideAsync("Mozilla/5.0 (Linux; Android 6.0.1; Nexus 7 Build/MOB30X) AppleWebKit/5(KHTML,likeGeckoChrome/89.0.4389.114Safari/537.36", null, null, ua);
}
var userAgent = await browser.EvaluateScriptAsync("navigator.userAgent");
Assert.True(userAgent.Success);
Assert.Contains("Mozilla/5.0 (Linux; Android 6.0.1; Nexus 7 Build/MOB30X) AppleWebKit/5(KHTML,likeGeckoChrome/89.0.4389.114Safari/537.36", Assert.IsType<string>(userAgent.Result));
var brands = await browser.EvaluateScriptAsync("navigator.userAgentData.brands");
Assert.True(brands.Success);
dynamic brandsResult = brands.Result;
Assert.Collection((IEnumerable<dynamic>)brandsResult,
(dynamic d) =>
{
Assert.Equal("Google Chrome", d.brand);
Assert.Equal("89", d.version);
},
(dynamic d) =>
{
Assert.Equal("Chromium", d.brand);
Assert.Equal("89", d.version);
}
);
var highEntropyValues = await browser.EvaluateScriptAsPromiseAsync("return navigator.userAgentData.getHighEntropyValues(['architecture','model','platform','platformVersion','uaFullVersion'])");
Assert.True(highEntropyValues.Success);
dynamic highEntropyValuesResult = highEntropyValues.Result;
Assert.Equal("arm", highEntropyValuesResult.architecture);
Assert.Equal("Nexus 7", highEntropyValuesResult.model);
Assert.Equal("Android", highEntropyValuesResult.platform);
Assert.Equal("6.0.1", highEntropyValuesResult.platformVersion);
Assert.Equal("89.0.4389.114", highEntropyValuesResult.uaFullVersion);
}
}
DevTools - Support strongly typed events (#3669) Includes various other DevTools fixes: - JavaScript "number"s are represented as doubles instead of longs - Headers are now correctly serialized / deserialized - DevToolsDomainErrorResponse is now correctly deserialized
2021-07-05 02:32:22 +02:00
[Fact]
public async Task CanSetExtraHTTPHeaders()
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("about:blank", automaticallyCreateBrowser: false, useLegacyRenderHandler: false))
DevTools - Support strongly typed events (#3669) Includes various other DevTools fixes: - JavaScript "number"s are represented as doubles instead of longs - Headers are now correctly serialized / deserialized - DevToolsDomainErrorResponse is now correctly deserialized
2021-07-05 02:32:22 +02:00
{
await browser.CreateBrowserAsync();
using (var devToolsClient = browser.GetDevToolsClient())
{
var extraHeaders = new Headers();
extraHeaders.SetCommaSeparatedValues("TEST", "0");
extraHeaders.AppendCommaSeparatedValues("test", " 1 ", "\" 2 \"");
extraHeaders.AppendCommaSeparatedValues("Test", " 2,5 ");
await devToolsClient.Network.SetExtraHTTPHeadersAsync(extraHeaders);
DevTools Client - Add Event error handling - New event that is raised when an exception occurs during converting a response to JSON - Test cleanup - New unit test to validate IEventProxy has been removed from ConcurrentDictionary Resolves #3787
2021-09-10 14:10:18 +10:00
var evtTask = Assert.RaisesAsync<RequestWillBeSentEventArgs>(
x => devToolsClient.Network.RequestWillBeSent += x,
x => devToolsClient.Network.RequestWillBeSent -= x,
async () =>
DevTools - Support strongly typed events (#3669) Includes various other DevTools fixes: - JavaScript "number"s are represented as doubles instead of longs - Headers are now correctly serialized / deserialized - DevToolsDomainErrorResponse is now correctly deserialized
2021-07-05 02:32:22 +02:00
{
DevTools Client - Add Event error handling - New event that is raised when an exception occurs during converting a response to JSON - Test cleanup - New unit test to validate IEventProxy has been removed from ConcurrentDictionary Resolves #3787
2021-09-10 14:10:18 +10:00
// enable events
await devToolsClient.Network.EnableAsync();
await browser.LoadUrlAsync("www.google.com");
});
var xUnitEvent = await evtTask;
Assert.NotNull(xUnitEvent);
var args = xUnitEvent.Arguments;
Assert.NotNull(args);
Assert.NotEmpty(args.RequestId);
Assert.NotEqual(0, args.Timestamp);
Assert.NotEqual(0, args.WallTime);
Assert.NotNull(args.Request);
Assert.True(args.Request.Headers.TryGetValues("TeSt", out var values));
Assert.Collection(values,
v => Assert.Equal("0", v),
v => Assert.Equal("1", v),
v => Assert.Equal(" 2 ", v),
v => Assert.Equal(" 2,5 ", v)
);
}
DevTools - Support strongly typed events (#3669) Includes various other DevTools fixes: - JavaScript "number"s are represented as doubles instead of longs - Headers are now correctly serialized / deserialized - DevToolsDomainErrorResponse is now correctly deserialized
2021-07-05 02:32:22 +02:00
}
}
[Fact]
public async Task ExecuteDevToolsMethodThrowsExceptionWithInvalidMethod()
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("www.google.com", useLegacyRenderHandler: false))
DevTools - Support strongly typed events (#3669) Includes various other DevTools fixes: - JavaScript "number"s are represented as doubles instead of longs - Headers are now correctly serialized / deserialized - DevToolsDomainErrorResponse is now correctly deserialized
2021-07-05 02:32:22 +02:00
{
Core - Rename WaitForBrowserInitialLoadAsync to WaitForInitialLoadAsync and simplify - Initial intention was to have a reusable method that could be used CefSharp.Wpf.HwndHost, upon further deliberation I've decided to build the functionality into the ChromiumWebBrowser.Partial.cs and will need to duplicate the functionality in CefSharp.Wpf.HwndHost. This guarantees that the Task will be resolved in all cases. The previous implementation there was a theoretical change we'd miss subscribing to the relevant events - Remove CancellationToken as it's not possible to cancel Issue #3842
2021-10-28 10:30:03 +10:00
await browser.WaitForInitialLoadAsync();
DevTools - Support strongly typed events (#3669) Includes various other DevTools fixes: - JavaScript "number"s are represented as doubles instead of longs - Headers are now correctly serialized / deserialized - DevToolsDomainErrorResponse is now correctly deserialized
2021-07-05 02:32:22 +02:00
using (var devToolsClient = browser.GetDevToolsClient())
{
DevTools Client - Generic ExecuteDevToolsMethodAsync and add RegisterEventHandler (#3674) * Make ExecuteDevToolsMethodAsync generic * Make RegisterEventHandler generic * PR feedback and added test for registering multiple event handlers * Updated generated code to latest version * Fix possible NRE when removing event listener before adding one
2021-07-26 04:01:46 +02:00
var ex = await Assert.ThrowsAsync<DevToolsClientException>(
DevTools - Support strongly typed events (#3669) Includes various other DevTools fixes: - JavaScript "number"s are represented as doubles instead of longs - Headers are now correctly serialized / deserialized - DevToolsDomainErrorResponse is now correctly deserialized
2021-07-05 02:32:22 +02:00
() => devToolsClient.ExecuteDevToolsMethodAsync("methoddoesnotexist"));
Assert.NotNull(ex.Response);
Assert.NotEqual(0, ex.Response.MessageId);
Assert.NotEqual(0, ex.Response.Code);
Assert.NotNull(ex.Response.Message);
}
}
}
DevTools Client - Generic ExecuteDevToolsMethodAsync and add RegisterEventHandler (#3674) * Make ExecuteDevToolsMethodAsync generic * Make RegisterEventHandler generic * PR feedback and added test for registering multiple event handlers * Updated generated code to latest version * Fix possible NRE when removing event listener before adding one
2021-07-26 04:01:46 +02:00
Test - Add DevToolsClientFacts MediaQuery test
2022-03-22 16:46:04 +10:00
[Fact]
public async Task CanGetMediaQueries()
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("https://cefsharp.github.io/demo/mediaqueryhover.html", useLegacyRenderHandler: false))
Test - Add DevToolsClientFacts MediaQuery test
2022-03-22 16:46:04 +10:00
{
await browser.WaitForInitialLoadAsync();
using (var devToolsClient = browser.GetDevToolsClient())
{
await devToolsClient.DOM.EnableAsync();
await devToolsClient.CSS.EnableAsync();
var mediaQueries = await devToolsClient.CSS.GetMediaQueriesAsync();
Assert.True(mediaQueries.Medias.Count > 0);
}
}
}
DevTools Client - Generic ExecuteDevToolsMethodAsync and add RegisterEventHandler (#3674) * Make ExecuteDevToolsMethodAsync generic * Make RegisterEventHandler generic * PR feedback and added test for registering multiple event handlers * Updated generated code to latest version * Fix possible NRE when removing event listener before adding one
2021-07-26 04:01:46 +02:00
[Fact]
public async Task CanRegisterMultipleEventHandlers()
{
OffScreen - Add useLegacyRenderHandler optional param to constructor - Defaults to true - For those using CaptureScreenshotAsync set to false to avoid creating DefaultRenderHandler
2023-01-15 11:33:08 +10:00
using (var browser = new ChromiumWebBrowser("about:blank", automaticallyCreateBrowser: false, useLegacyRenderHandler: false))
DevTools Client - Generic ExecuteDevToolsMethodAsync and add RegisterEventHandler (#3674) * Make ExecuteDevToolsMethodAsync generic * Make RegisterEventHandler generic * PR feedback and added test for registering multiple event handlers * Updated generated code to latest version * Fix possible NRE when removing event listener before adding one
2021-07-26 04:01:46 +02:00
{
await browser.CreateBrowserAsync();
using (var devToolsClient = browser.GetDevToolsClient())
{
DevToolsEventArgs devToolsEventArgs = null;
EventHandler<DevToolsEventArgs> devToolsEventHandler = (sender, args) =>
{
if (devToolsEventArgs == null)
{
devToolsEventArgs = args;
}
};
devToolsClient.DevToolsEvent += devToolsEventHandler;
RequestWillBeSentEventArgs requestWillBeSentEventArgs1 = null;
EventHandler<RequestWillBeSentEventArgs> requestWillBeSentEventHandler1 = (sender, args) =>
{
if (requestWillBeSentEventArgs1 == null)
{
requestWillBeSentEventArgs1 = args;
}
};
devToolsClient.Network.RequestWillBeSent += requestWillBeSentEventHandler1;
RequestWillBeSentEventArgs requestWillBeSentEventArgs2 = null;
EventHandler<RequestWillBeSentEventArgs> requestWillBeSentEventHandler2 = (sender, args) =>
{
if (requestWillBeSentEventArgs2 == null)
{
requestWillBeSentEventArgs2 = args;
}
};
devToolsClient.Network.RequestWillBeSent += requestWillBeSentEventHandler2;
// enable events
await devToolsClient.Network.EnableAsync();
await browser.LoadUrlAsync("www.google.com");
Assert.NotNull(devToolsEventArgs);
Assert.NotNull(requestWillBeSentEventArgs1);
Assert.NotNull(requestWillBeSentEventArgs2);
Assert.Equal(requestWillBeSentEventArgs1.RequestId, requestWillBeSentEventArgs2.RequestId);
// remove second event handler
devToolsClient.Network.RequestWillBeSent -= requestWillBeSentEventHandler2;
devToolsEventArgs = null;
requestWillBeSentEventArgs1 = null;
requestWillBeSentEventArgs2 = null;
await browser.LoadUrlAsync("www.google.com");
Assert.NotNull(devToolsEventArgs);
Assert.NotNull(requestWillBeSentEventArgs1);
Assert.Null(requestWillBeSentEventArgs2);
}
}
}
[Fact]
DevTools Client - Add Event error handling - New event that is raised when an exception occurs during converting a response to JSON - Test cleanup - New unit test to validate IEventProxy has been removed from ConcurrentDictionary Resolves #3787
2021-09-10 14:10:18 +10:00
public void CanRemoveEventListenerBeforeAddingOne()
DevTools Client - Generic ExecuteDevToolsMethodAsync and add RegisterEventHandler (#3674) * Make ExecuteDevToolsMethodAsync generic * Make RegisterEventHandler generic * PR feedback and added test for registering multiple event handlers * Updated generated code to latest version * Fix possible NRE when removing event listener before adding one
2021-07-26 04:01:46 +02:00
{
DevTools Client - Add Event error handling - New event that is raised when an exception occurs during converting a response to JSON - Test cleanup - New unit test to validate IEventProxy has been removed from ConcurrentDictionary Resolves #3787
2021-09-10 14:10:18 +10:00
using (var devToolsClient = new DevToolsClient(null))
DevTools Client - Generic ExecuteDevToolsMethodAsync and add RegisterEventHandler (#3674) * Make ExecuteDevToolsMethodAsync generic * Make RegisterEventHandler generic * PR feedback and added test for registering multiple event handlers * Updated generated code to latest version * Fix possible NRE when removing event listener before adding one
2021-07-26 04:01:46 +02:00
{
DevTools Client - Add Event error handling - New event that is raised when an exception occurs during converting a response to JSON - Test cleanup - New unit test to validate IEventProxy has been removed from ConcurrentDictionary Resolves #3787
2021-09-10 14:10:18 +10:00
devToolsClient.Network.RequestWillBeSent -= (sender, args) => { };
}
}
DevTools Client - Generic ExecuteDevToolsMethodAsync and add RegisterEventHandler (#3674) * Make ExecuteDevToolsMethodAsync generic * Make RegisterEventHandler generic * PR feedback and added test for registering multiple event handlers * Updated generated code to latest version * Fix possible NRE when removing event listener before adding one
2021-07-26 04:01:46 +02:00
DevTools Client - Add Event error handling - New event that is raised when an exception occurs during converting a response to JSON - Test cleanup - New unit test to validate IEventProxy has been removed from ConcurrentDictionary Resolves #3787
2021-09-10 14:10:18 +10:00
[Fact]
public void IsIEventProxyRemovedFromConcurrentDictionary()
{
const string eventName = "Browser.downloadProgress";
using (var devToolsClient = new DevToolsClient(null))
{
EventHandler<DownloadProgressEventArgs> eventHandler1 = (object sender, DownloadProgressEventArgs args) => { };
EventHandler<DownloadProgressEventArgs> eventHandler2 = (object sender, DownloadProgressEventArgs args) => { };
devToolsClient.AddEventHandler(eventName, eventHandler1);
devToolsClient.AddEventHandler(eventName, eventHandler2);
var hasHandlers = devToolsClient.RemoveEventHandler(eventName, eventHandler1);
Assert.True(hasHandlers);
hasHandlers = devToolsClient.RemoveEventHandler(eventName, eventHandler2);
Assert.False(hasHandlers);
DevTools Client - Generic ExecuteDevToolsMethodAsync and add RegisterEventHandler (#3674) * Make ExecuteDevToolsMethodAsync generic * Make RegisterEventHandler generic * PR feedback and added test for registering multiple event handlers * Updated generated code to latest version * Fix possible NRE when removing event listener before adding one
2021-07-26 04:01:46 +02:00
}
}
Enhancement - Add DevToolsClient (#3229) * Core - Add DevToolsClient Issue #3165 * DevTools Client - Add Network domain class - Add hand written class to get a better sense of how the code should be structured. - Improve exception handling * Devtools - First draft of devtools protocol methods (generated) Not complete yet * Devtools - Simple method execution working * DevTools - Add .Net Style cased property names to response objects - Use internal field and datacontract attributes * DevTools - Improve mapping * DevTools - Strongly typed enums * DevTools Client - Generated from active browser instance (M84) * Devtools Client - Extract IDevToolsClient interface for testability Improve xml doc comments * DevTools Client - Improve error handling * DevTools Client - Improve enum conversion * Revert to older c# syntax * DevTools Client - Fix failing tests * Devtools Client - Add SetCookie Tests * DevTools Client - Add Capture SyncContext by default - Add option to capture the SyncContext - Add option to provide custom SyncContext (can just pass in UI SyncContext and all continuations will happen there). - Fix bug in ExecuteDevToolsMethodAsync sending the command twice when exeucted on the CEF UI thread * Devtools Client - Add missing file reference The problem with developing with the .Net Core project where files are automatically included is you forget to include them in the regular csproj file. * Devtools Client - Add CanCanEmulate Test case * DevTools Client - Add AddScriptToEvaluateOnNewDocumentAsync test * DevTools Client - OnDevToolsEvent only parse data if event handler != null * DevTools Client - GetDevToolsClient remove ThrowExceptionIfDisposed/ThrowExceptionIfBrowserNotInitialized calls Those methods were removed as the GetBrowser call handles the checks for us. * DevTools Client - Improve error handling * DevTools Client - Update xml doc comments * DevTools Client - Add validation method (partial) Add ability to manually add validation logic * DevTools Client - Comment out failing test Was working when targeting M84, now with M85 it fails. The mapping appears to be correct, will need to investigate further * OffScreen Example - Remove test code
2020-09-21 19:32:25 +10:00
}
}
Reference in New Issue Copy Permalink