tldr; Browser Source plugin is prepending local paths with a non-standard prefix, which stops local HTML files from being able to view local images.
I'm working on a local webpage for use in OBS, via the Browser Source plugin.
It is a local webpage, and uses local files and images. So in the URL bar of Chrome it shows:
I should say that it shows the file:/// prefix after double clicking in the address bar.
In the Browser Source plugin, I just click "Local" and browse on my file system to the HTML file, which returns the local path.
A few weeks ago it was working fine. The local http file would show the local images in both Chrome and OBS Browser Source.
Today I was back working on this, and all was fine in Chrome.
But OBS now refused to display those images. And in the log was an error about:
After some searching, it looked like it was the security in the browser stopping files being loaded, because the root URL isn't the same.
My images were showing as file:///c:/ ETC.....
And the http file was showing in the log as:
I could change the image prefixes to have http://absolute/ at the front. Then it worked in OBS. But then it stopped working in Chrome.
Again, because Chrome couldn't access the images. Because of the http://absolute/ I added in front.
And no web browser will accept http://absolute/ as a prefix for a local file.
So my current solution that works is to leave the images with file:/// prefix.
Then in the Browser Source settings, UNTICK local, and simply put the URL to the http page with file:/// at the front.
This works.
However, we shouldn't have to do this. WHY is Browser Source adding http://absolute/ at the front? I cannot find any reference online to that being a special URL.
Please put it back to using the standard notation of file:/// for local files.
That's standard, and works when we have local http files, and local image resources.
I'm working on a local webpage for use in OBS, via the Browser Source plugin.
It is a local webpage, and uses local files and images. So in the URL bar of Chrome it shows:
I should say that it shows the file:/// prefix after double clicking in the address bar.
In the Browser Source plugin, I just click "Local" and browse on my file system to the HTML file, which returns the local path.
A few weeks ago it was working fine. The local http file would show the local images in both Chrome and OBS Browser Source.
Today I was back working on this, and all was fine in Chrome.
But OBS now refused to display those images. And in the log was an error about:
After some searching, it looked like it was the security in the browser stopping files being loaded, because the root URL isn't the same.
My images were showing as file:///c:/ ETC.....
And the http file was showing in the log as:
I could change the image prefixes to have http://absolute/ at the front. Then it worked in OBS. But then it stopped working in Chrome.
Again, because Chrome couldn't access the images. Because of the http://absolute/ I added in front.
And no web browser will accept http://absolute/ as a prefix for a local file.
So my current solution that works is to leave the images with file:/// prefix.
Then in the Browser Source settings, UNTICK local, and simply put the URL to the http page with file:/// at the front.
This works.
However, we shouldn't have to do this. WHY is Browser Source adding http://absolute/ at the front? I cannot find any reference online to that being a special URL.
Please put it back to using the standard notation of file:/// for local files.
That's standard, and works when we have local http files, and local image resources.