|
| 1 | +v4.0.0rc1 |
| 2 | +========= |
| 3 | + * Set available versions of Chrome DevTools Protocol to 85, 91, and 92. |
| 4 | + * Enabled script pinning. This allows the user to add a snippet of JavaScript |
| 5 | + to a page that will be available on all subsquent pages, and not have to |
| 6 | + pass the script across the wire every time. For exceptionally large blobs |
| 7 | + of JavaScript, this may represent a significant savings in bandwidth and |
| 8 | + data sent to the remote end of the WebDriver protocol. This feature is |
| 9 | + currently only available for browsers that implement the Chrome DevTools |
| 10 | + Protocol. |
| 11 | + * Added ability to use By object with relative locators. This change also |
| 12 | + marks RelativeBy.WithTagName as obsolete. Users should change their calls |
| 13 | + to `RelativeBy.WithLocator(By.TagName(...))`. |
| 14 | + * Allow network interception to handle duplicate response headers. |
| 15 | + Headers in HTTP responses may be repeated. The previous implementation |
| 16 | + of CDP network response handling did not take this into account. Now, if |
| 17 | + a response has duplicate headers, the values will be combined into a |
| 18 | + single header with the correct name, and a comma-separated list for the |
| 19 | + value. This is complaint with RFC2616. There is an exception for the |
| 20 | + Set-Cookie header, however, which is allowed to occur multiple times, |
| 21 | + but is not combinable as to the rules of the aforementioned RFC. To |
| 22 | + account for this, a new property on HttpResponseData has been added to |
| 23 | + list the cookie headers (the `CookieHeaders` property) as found in the |
| 24 | + response. |
| 25 | + |
1 | 26 | v4.0.0b4
|
2 | 27 | ========
|
3 | 28 | * 4.0.0b3 was skipped for the .NET bindings and not released publicly.
|
|
0 commit comments