To clarify: I think, it's legitimate to let the author know that their content fails to render on one of the three major browsers (and displays a blank content area, instead). Similar messages regarding basic interoperability are seen here all the time.
And yes, I find it remarkable that GitHub should fail over a content security error on an active and updated browser engine, which is by no means exotic. I wouldn't have expected this to happen. There may be also a broader issue, which may affect other content, as well.
(None of this is intended to trigger any issues with product identification or anger regarding any platforms or browser vendors.)
BTW: Firefox 118.02 throws a Content-Security-Policy error, as well, but still renders the content, while reporting several issues with the Referrer Policy. (Arguably, it should fail to render in case of a detected content security policy violation.)
And yes, I find it remarkable that GitHub should fail over a content security error on an active and updated browser engine, which is by no means exotic. I wouldn't have expected this to happen. There may be also a broader issue, which may affect other content, as well.
(None of this is intended to trigger any issues with product identification or anger regarding any platforms or browser vendors.)
BTW: Firefox 118.02 throws a Content-Security-Policy error, as well, but still renders the content, while reporting several issues with the Referrer Policy. (Arguably, it should fail to render in case of a detected content security policy violation.)