obsproject / obsproject/obs-browser
Per-instance BrowserSource Chromium Flags
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 904
- Forks
- 267
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
I know that you can pass flags to the Chromium instance via opening obs with them but this isn't ideal from a security standpoint.
My current use case is I have two BrowserSource instances, one for a local page that can be whole-heartedly trusted while another, which points to a remote site, that can't be. I'd like to be able to pass the --disable-web-security flag to the local-page's instance, while the remote-page instance would still enforce such.
I'd suggest an additional input box for specifying flags below the custom CSS input.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how each BrowserSource instance is created and how Chromium flags are currently passed to the shared instance. Determine where per-instance flag configuration belongs and how the existing BrowserSource settings are exposed. Done means a local instance can use its configured flags without changing the flags or security behavior of another instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100