Releases: seclerp/dotnet-chrome-protocol
Releases · seclerp/dotnet-chrome-protocol
2.1.0
Added
ChromeProtocol.Runtime.Browser.ChromiumLauncher
class that simplifies starting Chrome and obtaining debugging endpoint- Simple example project
ChromeProtocol.Usage
that highlights usage of theChromeProtocol.Runtime
andChromeProtocol.Domains
libraries
Removed
ChromeProtocol.Runtime.Messaging.Logger.ChannelProtocolClientLogger
Changed
ProtocolClientLogger.LogConnected
becameprotected
ProtocolClientLogger.LogDisconnected
becameprotected
ProtocolClientLogger.LogOutgoingRequest
becameprotected
ProtocolClientLogger.LogIncomingResponse
becameprotected
ProtocolClientLogger.LogIncomingUnknownResponse
becameprotected
ProtocolClientLogger.LogIncomingError
becameprotected
ProtocolClientLogger.LogIncomingEvent
becameprotected
ChromeProtocol.Core.Extensions.ReflectionExtensions
becameinternal
System.Text.Json
has been updated to the version8.0.5
to address high-severity vulnerabilities
Fixed
- Different typos and confusing
[Obsolete]
attributes - Multiple nullability issues in different places across packages
Changelog file can be found here.
NuGet links:
2.0.1
Changed
- Bump Domains version to Chrome base revision 1367902
- Reflect revision in the Domains package version
Changelog file can be found here.
NuGet links:
2.0.0
1.3.0
1.2.3
Fixed
- Fix binary inconsistency between different origins of the packages in different package sources
Changelog file can be found here.
NuGet links:
1.2.2
Fixed
- Fix missing copyright info in the NuGet packages metadata
Changelog file can be found here.
NuGet links:
1.2.1
Fixed
- Fix missing handling of invalid socket state while sending WebSocket requests
- Fix missing disconnect event invocation
Changelog file can be found here.
NuGet links:
1.2.0
Added
- Add
SessionId
parameter forSubscribeAsync
andSubscribeSync
methods ofProtocolClient
Fixed
- Fix Subscribe methods replicating events for all connected sessions
Changelog file can be found here.
NuGet links: