Hi,
I wonder if anyone can help. We are using vaadin 7.4.2 with the addon vaadin-wrapper-for-tinymce 3.0
I am building a layout (extending VerticalLayout) that contains a single tabsheet. Within the tabsheet:
the first tab is a VerticalLayout which in turn has a single component being an instance of TinyMCETextField
the 2nd tab is an empty VertcialLayout
the 3rd tab is an empty VeritcalLayout
When the browser renders the page, the first tab is display and the TinyMCE editor is correctly rendered.
When I change tab the correct tab is shown (albeit empty for now)
When I change back to the first tab (the one with the TinyMCE editor), the content of the editor is displayed within a div, but the TinyMCE editor is not displayed. Using chrome dev tools to inspect the dom, it looks like the div with the content is showing because the TinyMCE javascript has not been executed (or more accurately, re-executed ?)
Does anyone know how I can get the TinyMCE editor to re-render correctly when I switch tabs?
Hi
I’m having the same problem, however a completely different scenario, I’m using it in cuba framework. The screens are organized as tabsheet. When I open a screen where there are TinyMCE boxes, everything looks fine, however if I change to a different tab, and then come back, all the tinyMCE boxes disappear, in place of each there will be a disabled textbox…
the error message in the console is
Uncaught TypeError: Cannot read property 'fire' of undefined
at Array.<anonymous> (cdn.tinymce.com/4/tinymce.min.js?v=2017_02_07_16_37:12)
at n (cdn.tinymce.com/4/tinymce.min.js?v=2017_02_07_16_37:3)
at d (cdn.tinymce.com/4/tinymce.min.js?v=2017_02_07_16_37:12)
at e (cdn.tinymce.com/4/tinymce.min.js?v=2017_02_07_16_37:2)
at m (cdn.tinymce.com/4/tinymce.min.js?v=2017_02_07_16_37:2)
It might relate to
this error, but I don’t really understand which id are they talking about. As I see the generated component has an alphanumerical id:
Because of not being able to tab switch, not being able to configure key editor features (ie. any use of the setup hook), and not getting any suggestions from Vaadin, the community, or the add-on author (who works for Vaadin); we have concluded that this add-on doesnt work very well, has not been properly tested with real world scenarios, and is certainly not production ready.
No, I’m not tied to it, and it seems to be a great sugestion, thank you! If it works as you say, I will replace it efinitely.
However today I’ve made a workaround, which was basically detecting the tabchange, and then throw away and reinit the tinyMCE components.
Thank you for your suggestion, I will look into it soon!