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
I observed issue of Trumbowyg crashing the page despite latest version https://github.com/Alex-D/Trumbowyg/releases/tag/v2.25.1, which had supposedly fixed an issue #1233 (fixed in 5ad49f3) that seems to be related based on the error message (TypeError: Range.setEnd: Argument 1 does not implement interface Node.). As the fix replaced t.range.startContainer.parentNode by t.range, I suspect that a similar check needs to be performed at
Note that I'm unable to reproduce this intentionally, and I don't have any debugging setup in place to discover the conditions or root cause. This doesn't usually occur (but it's fatal when it does, causing a motivation to wrap this component in some Vue error boundary - too bad https://github.com/ankurk91/vue-trumbowyg is archived so it can't be done there). I currently don't have any more information except the following screenshot(s):
It has occurred again, so at least I confirmed some variables in debugger:
Description
Microsoft Windows 10 Enterprise
Firefox 91.0.1 (64-bit)
The text was updated successfully, but these errors were encountered:
I observed issue of Trumbowyg crashing the page despite latest version https://github.com/Alex-D/Trumbowyg/releases/tag/v2.25.1, which had supposedly fixed an issue #1233 (fixed in 5ad49f3) that seems to be related based on the error message (
TypeError: Range.setEnd: Argument 1 does not implement interface Node.
). As the fix replacedt.range.startContainer.parentNode
byt.range
, I suspect that a similar check needs to be performed atTrumbowyg/src/trumbowyg.js
Line 1831 in fd304a3
Note that I'm unable to reproduce this intentionally, and I don't have any debugging setup in place to discover the conditions or root cause. This doesn't usually occur (but it's fatal when it does, causing a motivation to wrap this component in some Vue error boundary - too bad https://github.com/ankurk91/vue-trumbowyg is archived so it can't be done there). I currently don't have any more information except the following screenshot(s):
It has occurred again, so at least I confirmed some variables in debugger:
Description
The text was updated successfully, but these errors were encountered: