HTML Description Tinymce v5 Issues - Help needed

[raycallan]

We upgraded our instance to Tokyo last night and while everything went well as a whole, one issue that was immediately highlighted was the the HTML description fields were not working as expected. Instead of have two lines of icons there was only one line and the ability to right click in the editor window and paste is gone.

I quickly identified that the editor had been upgraded from Tinymce v4 to Tinymce v5 and I referred to the latest documentation for Tokyo and it only references Tinymce v4

Issue 1 - Missing icons - Resloved

I opened the system properties list, filtered the list to 'glide.ui.html.editor'  after a bit of trial any error I discovered that Tinymce v5 no longer support line 1 and line 2. However I was able copy the values from 'glide.ui.html.editor.v4.toolbar.line1' and 'glide.ui.html.editor.v4.toolbar.line2' and merge them into 'glide.ui.html.editor.v5.toolbar' and the editor displayed all the icons and automatically onto 2 lines. I did have to replace all the commas with spaces as v5 no longer suppots comma delimited

Issue 2 - Unable to right click and paste - Ongoing

Unfortunately, I have not been able to resolve this and instead of getting the browsers supported paste functionality. I only get the ability to link as per below. I can't find any documentation to fix this so I'm hoping someone in the community can help

Thanks in advance

Ray

[Mike_R · Accepted solution]

Someone else reported the same issuing with pasting

https://www.servicenow.com/community/sysadmin-forum/paste-option-missing-in-email-compose-screen-sho...

This is what i told them

"As a workaround, if you hold down Ctrl and right click then you see the normal paste/other options. And obviously CTRL + v works too.

I don't see anything documented on ServiceNow's site regarding this, so i would suggest opening a case with Support."

I would highly suggest opening a case with SN support. The more people that report this issue to them, the better chance they fix it soon!

[Alexandra Dickm]

Having the exact same issue. I hope in the 4 weeks since posting you've gotten a response from ServiceNow?

[J_r_my1]

Might be a bit late.

But you can add in the attribute : editor.plugins=contextmenu:false

If you want to have the possibility to have pictures/table, you can add editor.plugins=contextmenu:false image table media

[Astrid Sapphire]

I did a bit of experimentation and am able to provide an example of how to set contextmenu false if needed. Keep in mind that this is custom functionality, so your mileage may vary and you need to maintain it. 

The below is called from a client script (set 'Isolate Script' to false) or UI script (drop the onLoad wrapping function):

function onLoad() {
	window.onload = function() {
	if(tinyMCE !== undefined && tinyMCE.editors !== undefined) //TinyMCE is present and has editors (has been initialised)
		tinyMCE.editors[tinyMCE.activeEditor.id].settings.contextmenu = false;
		tinyMCE.editors[tinyMCE.activeEditor.id].load(); // Triggers reload
	};
}

You'll note I use the active editor id (which is table_name.field) - you can also reference by it's index in the editors array, replacing the activeEditor check with 0. The same applies for doing this where you have multiple editors on a page, see below:

function onLoad() {
	window.onload = function() {
	if(tinyMCE !== undefined && tinyMCE.editors !== undefined) //TinyMCE is present and has editors (has been initialised)
		for(var i = 0; i < tinyMCE.editors.length; i++){
			tinyMCE.editors[i].settings.contextmenu = false;
			tinyMCE.editors[i].load(); // Triggers reload
		}
	};
}

In my instance this had an imperceptible impact on performance, and resolved within a millisecond - but as ever, this is dealing with UI scripting so beware 🙂

Good luck!

[Noel6]

Thank you Astrid! Thats very helpful. 

There is an related idea regarding this here: 

https://support.servicenow.com/now?id=view_idea&sysparm_idea_id=f7ac93091b879510acdc54e56b4bcb41&sys...

[Adam Warner]

Lovely stuff, and very helpful indeed. Hopefully the ServiceNow devs give us an option to customise/disable the context menu natively in future... 🤞