Reply to thread

First, if you really are running Beta 1, please confirm the issue with the latest version.


Beyond that, we may need a reduced test case and/or more information about the specific situation that has caused this. The only situation I can think of is where the Froala instance hasn't been initialized yet. In most scenarios, this would be a race condition or your code doing something unexpected in editor:start for example. Alternatively, this could be a situation where the editor init has been deferred, though it's not clear if that's relevant (it's only done in a small number of situations).


Back
Top Bottom