obsproject / obsproject/obs-studio
obs-browser: Use CEF official methods of replacing/disabling error pages
Open
Nobody has claimed this yet.
area/dependency
- Dominant language
- C
- Stars
- 76.4k
- Forks
- 10.2k
- Avg merge
- 4d 23h
- Merged PRs (30d)
- 12
Description
With the update to the Chrome Runtime, browser sources will begin showing vanilla Chrome error pages.
To bypass this, the obs-browser commit to enable Chrome Runtime hardcodes a navigation to about:blank.
Once CEF has a valid API to do this properly, switch over to it.
Contributor guide
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 reviewing the obs-browser change that enabled Chrome Runtime and its hardcoded about:blank navigation; check CEF issue 3852 for the official API status and obs-browser pull request 523 for context. Replace the workaround when CEF exposes a valid method, and verify browser sources no longer show vanilla Chrome error pages.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop-dev, web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100