Webpage that performs redirects becomes invisible #438
Labels
No labels
area/accessibility
area/dependency
Confirmed
Crash Report
Delayed
Design Issue
Duplicate
Feedback required
Good first issue
kind/bug
kind/cleanup
kind/enhancement
platform/linux
platform/macos
platform/windows
priority/high
Question
Request for Comments
Seeking Other Contributors
Seeking Testers
Won't Fix / By Design
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-obsproject/obs-browser#438
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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; }betweenrgba(0, 0, 0, 0)andrgba(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
There is definitely something very weird happening here. The page still renders in devtools but not in OBS
Forcing the page to navigate to another URL such as Google and then issuing a
history.back()command the page then functions fine.I have the same issue on my own implementation of cef. this happens only when using
external_begin_frame = trueand the browser_id > 1. if the browser_id(1) is navigated or closed, the issue is fixed. Navigating browser_id > 1 will stall the video capture until navigated back or the browser_id(1) is navigated or closed.As a temporary workaround, at initialization im creating a browser instance and killing it right away.
related