Open ooker777 opened 2 years ago
Thanks for the report. I can reproduce this in Firefox as well. Chrome and Safari seem to be fine. This is caused by browser.render.js
from Viz.js, even though this should be the "browser-compatible" version of it.
So is it from Firefox or Viz?
On Thu, Mar 10, 2022, 00:44 Christian Voigt @.***> wrote:
Thanks for the report. I can reproduce this in Firefox as well. Chrome and Safari seem to be fine. This is caused by browser.render.js from Viz.js, even though this should be the "browser-compatible" version of it.
— Reply to this email directly, view it on GitHub https://github.com/christianvoigt/argdown/issues/332#issuecomment-1063191050, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABTCUXJWKGYW6GF4KALDY23U7DPRNANCNFSM5QJST2PA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID: @.***>
I think this is either a problem of Viz.js (though browser.render.js
should obviously work in the browser) or a bundling problem (the Sandbox is bundled with Webpack). But I will have to investigate this further.
So far I have no idea yet why this only occurs in Firefox.
Checking the console I get