Wysiwyg-editor: [3.1.0] `Uncaught TypeError: e is not a function` on fullscreen

[lovelyelfpop]

[AndreaGProg]

Same problem:

froala_editor.pkgd.min.js:7 Uncaught TypeError: e is not a function
at f (froala_editor.pkgd.min.js:7)
at Object.u [as toggle] (froala_editor.pkgd.min.js:7)
at E.Bootstrap.callback (froala_editor.pkgd.min.js:7)
at Object.n [as exec] (froala_editor.pkgd.min.js:7)
at o (froala_editor.pkgd.min.js:7)
at a (froala_editor.pkgd.min.js:7)
at t (froala_editor.pkgd.min.js:7)
at E.Bootstrap.c (froala_editor.pkgd.min.js:7)
at r (froala_editor.pkgd.min.js:7)
at HTMLButtonElement. (froala_editor.pkgd.min.js:7)

[skullacy]

Same problem too.

[kelvinmusselli]

Me too have this problem :(

[HerrDietz]

Same Problem here

[joscht]

Got the same problem with version 3.1.0. Unfortunately it's not just an error in the console, but the editor doesn't fill the complete screen.
If I don't override the toolbarButtons in the froala options, I still see the error in the console, but the editor fills the complete screen (which is not an option for us though because we want to override the toolbarButtons with something like this: toolbarButtons: [['fullscreen', 'bold']]).

Any updates on this issue? We're kinda blocked due to this.

[krissce]

Got the same full screen issue and error in console with Froala 3.1 when toolbarButtons is set to some custom value.

[ddoe8]

Having issues with this bug too.

[herumtreiber]

+1

[RantoniainaHairun]

+1

[hashina]

+1

Can you fix this asap guys?

[HerrDietz]

I wonder why so little happens here. The bug prevents us from replacing squire with froala.

Even in the rather minimal jsfiddle demo https://jsfiddle.net/froala/pruvo6j8/3/ the bug is reproducible (Chrome 80.0.3987.132). All you have to do is toggling fullscreen.

Please have look into it.

[dejanmartinovic]

The fix will be available in the next editor release. However, as the fix has already been added to the master branch, you can access it from here: https://cdn.jsdelivr.net/gh/froala/wysiwyg-editor@master/js/froala_editor.pkgd.min.js
https://jsfiddle.net/dejan_m/Lha56d3p/365/.

[trainbolt]

If anyone is interested the fix is pretty simple after tearing the code apart in 3.1.0

In plugins.pkgd.min.js:

Find
e=r.opts,o=e.height,e((t=r.opts,s=t.heightMax,t))((a=r.opts,l=a.z_index,a))

Replace with:
o=r.opts.height,s=r.opts.heightMax,l=r.opts.zIndex

In fullscreen.min.js:

Find
e=s.opts,i=e.height,e((t=s.opts,a=t.heightMax,t))((r=s.opts,l=r.z_index,r))

Replace with:
(i = s.opts.height),(a = s.opts.heightMax),(l = s.opts.zIndex),

The e() function is obviously incorrect whether that has anything to do with how the code was minimized or if it was an error in programming I'm not sure, but I am sure this fixes the issue.

Taking this long to fix an issue this small is completely ridiculous!

[robertvanhoesel]

This bug has apparently been fixed in 3.1.1, but not updated here.

Version 3.1.1
Release Date: Feb 23, 2020

• Fullscreen bug fixed
• FontFamily/fontSize output fixed
• Numerous performance improvements

[onedotover]

I'm on 3.2 and this does not seem to be fixed.

[shah20]

+1

[dejanmartinovic]

@robertvanhoesel @onedotover @shah20 The Uncaught TypeError: e is not a function on fullscreen - the problem is solved in version 3.1.1.
STRs:
Open this fiddle: https://jsfiddle.net/dejan_m/og0hxf2t/
Click the Fullscreen button
Check the console
result=> no errors

[dejanmartinovic]

If anyone is interested the fix is pretty simple after tearing the code apart in 3.1.0

In plugins.pkgd.min.js:

Find
e=r.opts,o=e.height,e((t=r.opts,s=t.heightMax,t))((a=r.opts,l=a.z_index,a))

Replace with:
o=r.opts.height,s=r.opts.heightMax,l=r.opts.zIndex

In fullscreen.min.js:

Find
e=s.opts,i=e.height,e((t=s.opts,a=t.heightMax,t))((r=s.opts,l=r.z_index,r))

Replace with:
(i = s.opts.height),(a = s.opts.heightMax),(l = s.opts.zIndex),

The e() function is obviously incorrect whether that has anything to do with how the code was minimized or if it was an error in programming I'm not sure, but I am sure this fixes the issue.

Taking this long to fix an issue this small is completely ridiculous!

This issue will be fixed in version 3.3.1. However, it is not related to this ticket.