Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: include vendor-prefixed security details #2405

Merged
merged 1 commit into from
Jul 11, 2024
Merged

Conversation

OrKoN
Copy link
Collaborator

@OrKoN OrKoN commented Jul 11, 2024

This PR adds vendor-prefixed security details to support Puppeteer use case until an alternative is part of the standard. The testing is planned via Puppeteer test suite.

@OrKoN OrKoN requested a review from Lightning00Blade July 11, 2024 09:38
@OrKoN OrKoN merged commit 414fa88 into main Jul 11, 2024
49 checks passed
@OrKoN OrKoN deleted the orkon/security-details branch July 11, 2024 09:41
@OrKoN OrKoN mentioned this pull request Jul 11, 2024
32 tasks
Lightning00Blade pushed a commit that referenced this pull request Jul 12, 2024
🤖 I have created a release *beep* *boop*
---


##
[0.6.1](chromium-bidi-v0.6.0...chromium-bidi-v0.6.1)
(2024-07-12)


### Features

* include vendor-prefixed additional request data
([#2406](#2406))
([76bce85](76bce85))
* include vendor-prefixed security details
([#2405](#2405))
([414fa88](414fa88))


### Bug Fixes

* default `beforeUnload` behavior is `accept`
([#2397](#2397))
([0d79f4b](0d79f4b))
* restore OOPiF state
([#2381](#2381))
([3e9855c](3e9855c))
* the capability to ignore cert errors should be browser-wide
([#2369](#2369))
([6db665b](6db665b))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: release-please[bot] <55107282+release-please[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants