In rare cases, the CORB warning message may indicate a problem on a website, which may disrupt its behavior when certain responses are blocked. For example, a response served with a "X-Content-Type-Options: nosniff" response header and an incorrect "Content-Type" response header may be blocked. This could, for example, block an actual image which is mislabeled as "Content-Type: text/html" and "nosniff." If this occurs and interferes with a page's behavior, we recommend informing the website and requesting that they correct the "Content-Type" header for the response.
So this is what is happening with bbb-playback. All the svg files likes shapes.svg files are loading. Only the slides[x].svg files are not loading.
This is beacause the shapes.svg files contains svg content and they are rendered as/or using svg dom elements.
But the slides[x].svg files are rendered as img dom elements. So there is a mismatch in the Content-Type as stated in the
documentation.
So I find here the solution to be any of the below stated two:
1. The bbb-playback source must be modified to render the slides[x].svg as svg dom elements.
2. Or, the bbb-record module must stick to the older method of processing the slides as png files.
I think the second choice is easier and an immediate fix for loading the CORS contents from S3 buckets, etc and to workaround CORB.
So, anybody please help how we switch back bbb-record module to render slides as png files.
Thanks & Regards