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
Every once in a while when I hit the "save" button on a form containing an ember-simplemde instance I get an error in the console that says TypeError: e.split is not a function and then the contents of the editor becomes [object Object].
Before the TypeError: I usually also see Assertion failed: Input argument is not an HTMLInputElement but I see that at other times even when the [object Object] problem does not happen, so I'm not sure if that's related or not.
So far I haven't been able to nail down any solid repro steps, it just seems to happen randomly. I'm hoping someone might have ideas on where I should be looking to nail down what's happening.
The text was updated successfully, but these errors were encountered:
Hey, the only e.split call in the code is in the unpackToolbarOptions that is called by buildSimpleMDEOptions during didInsertElement maybe there is an error there that is not being managed. I see that we only use that function if the var is string
all of this is in addon/components/simple-mde.js
Is it possible that you are changing the options from the component at runtime?
I'm also seeing this in tests when using fillIn('textarea', 'My value'). As per the trace above, the e.split error is originating from within simplemde.min.js. I'm not setting any options on my component so don't think it's related to that.
I've encountered this when upgrading my Ember app from 2.18 to 3.19. The tests passed fine on 2.18 - so not sure if you'd encounter it if the addon was upgraded to latest Ember version?
Every once in a while when I hit the "save" button on a form containing an ember-simplemde instance I get an error in the console that says
TypeError: e.split is not a function
and then the contents of the editor becomes[object Object]
.Before the
TypeError:
I usually also seeAssertion failed: Input argument is not an HTMLInputElement
but I see that at other times even when the[object Object]
problem does not happen, so I'm not sure if that's related or not.So far I haven't been able to nail down any solid repro steps, it just seems to happen randomly. I'm hoping someone might have ideas on where I should be looking to nail down what's happening.
The text was updated successfully, but these errors were encountered: