Refresh page if server was not available #71

New issue

Open

opened 2017-04-03 03:37:12 -05:00 by kutu · 3 comments

kutu commented

2017-04-03 03:37:12 -05:00

(Migrated from github.com)

if i use local server, and launch obs first, and only then my local server
obs doesn't refresh page after some timeout, if server was not available

in chrome, it shows "This site can’t be reached" page, and after some timeout it tries again

i wish there would be the same behaviour

if i use local server, and launch obs first, and only then my local server obs doesn't refresh page after some timeout, if server was not available in chrome, it shows "This site can’t be reached" page, and after some timeout it tries again i wish there would be the same behaviour

WizardCM commented

2019-12-27 17:55:17 -06:00

(Migrated from github.com)

This could be done via the OnLoadError event, based on the error code. I say it's a good idea.

This could be done via the [OnLoadError](https://magpcss.org/ceforum/apidocs/projects/(default)/CefLoadHandler.html#OnLoadError(CefRefPtr%3CCefBrowser%3E,CefRefPtr%3CCefFrame%3E,ErrorCode,constCefString&,CefString&)) event, based on the error code. I say it's a good idea.

WizardCM commented

2021-06-16 00:24:31 -05:00

(Migrated from github.com)

To work around this, there are now two solutions

We display a proper error screen on browser panels with a retry button
Browser sources & panels can be refreshed by the user using either the context menu on panels or the source toolbar for sources

To work around this, there are now two solutions 1. We display a proper error screen on browser panels with a retry button 2. Browser sources & panels can be refreshed by the user using either the context menu on panels or the source toolbar for sources

zaytri commented

2026-05-29 00:33:52 -05:00

(Migrated from github.com)

They could at that point refresh the related browser source and it would work, however there are many streamers who have a complex scene/source/group arrangement, making it not viable for them to have to find all of the related browser sources and manually refresh them. If there was a button to refresh all browser sources, that could be a somewhat viable workaround, otherwise people in those situations just have to close and reopen OBS.

And that's IF they even realize that their browser sources aren't working, considering several common overlays are empty at first (such as chat boxes, alert boxes, etc.). If at the very least a connection error is shown, then users could know to either refresh the sources or restart OBS before they start their stream. Without that, it's very easy for them to not notice until after they've started streaming.

I'm also concerned about this, as someone who's making a local app to run browser based overlays. It's pretty common for streamers to forget to open the app before opening OBS, and rather than showing any kind of error that it's unable to connect due to the app not being open, the browser source stays blank. Additionally, even when they do open the app and the local server starts running, it still stays blank, rather than showing what it should show from the local webpage. They could at that point refresh the related browser source and it would work, however there are many streamers who have a complex scene/source/group arrangement, making it not viable for them to have to find all of the related browser sources and manually refresh them. If there was a button to refresh all browser sources, that could be a somewhat viable workaround, otherwise people in those situations just have to close and reopen OBS. And that's IF they even realize that their browser sources aren't working, considering several common overlays are empty at first (such as chat boxes, alert boxes, etc.). If at the very least a connection error is shown, then users could know to either refresh the sources or restart OBS before they start their stream. Without that, it's very easy for them to not notice until after they've started streaming.

👍 1

No milestone

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

gh-obsproject/obs-browser#71

No description provided.

Rows
Columns