obsproject / obsproject/obs-browser
Webpage that performs redirects becomes invisible
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 904
- Forks
- 267
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 2
Description
Operating System Info
Windows 10
Other OS
No response
OBS Studio Version
30.1.1
OBS Studio Version (Other)
No response
OBS Studio Log URL
https://obsproject.com/logs/wOTzxKFaumzH09IZ
OBS Studio Crash Log URL
No response
Expected Behavior
Source displayed correctly after redirects.
Current Behavior
Redirects seem to confuse the browser source, and end up with an invisible source. Editing the custom CSS, e.g. tweaking body { background-color: rgba(0, 0, 0, 0; } between rgba(0, 0, 0, 0) and rgba(0, 0, 0, 1), the source will briefly flash visible then disappear again.
In this instance, the source is a page that does a redirect to Spotify for auth before redirecting back. If I relaunch OBS, where the auth has happened, so that a redirect isn't required, the browser source displays fine. Refreshing cache, making source enabled/disabled does not fix it, only relaunching OBS.
Steps to Reproduce
Add a browser source which does a redirect on load, e.g. https://jessicah.nz/spotify/now-playing.html
Anything else we should know?
No response
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 with the OBS browser source behavior using the provided reproduction URL and OBS log, focusing on what happens across the authentication redirects. Reproduce the invisible source on OBS 30.1.1 and compare it with a relaunch after authentication; done means the source remains visible after the redirect without requiring OBS to restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100