You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We get different results in between dev and build when linking the package into a solid app:
element.ownerDocument.documentElement is defined in dev mode, but is null when build.
When delaying it by a frame with requestAnimationFrame we do get the expected result:
When inlining it directly in the app, it also does not give an error, so it's a quite surprising bug. Afaik the bug also does not seem to show up when downloading the published library, only during linking (am i correct in this, @ralphsmith80 ?)
With the following snippet:
We get different results in between dev and build when linking the package into a solid app:
element.ownerDocument.documentElement
is defined in dev mode, but isnull
when build.When delaying it by a frame with
requestAnimationFrame
we do get the expected result:When inlining it directly in the app, it also does not give an error, so it's a quite surprising bug. Afaik the bug also does not seem to show up when downloading the published library, only during linking (am i correct in this, @ralphsmith80 ?)
a minimal reproduction of the bug
This bug came apparent during development of solid-plotly.js as
plotly-js
apparently makes use of this during initialisation.The text was updated successfully, but these errors were encountered: