We are using the TinyMCE control to handle formatted text in our web application. We support accented characters in our application. However, pasting accented characters into a field between other text (accented or not) causes IE8 to freeze and it must be restarted. If we paste into an empty field it works fine, if we paste at the beginning or end of the field it does not crash. It only crashes when pasting between other text. This does not happen in FireFox or Chrome.
I have identified the "paste" plugin as the problem, but we need to use this plugin to properly paste text from MS word into the application. I have not been able to find anything in TinyMCE's documentation or on their forum. I have posted a few things on their forum and I have not received any responses.
Does anyone else have this problem and a possible solution (other than don't use IE)?
Related
I had a few bookmarklets that used a technique like:
javascript:(function(){open('data:text/html,'+encodeURIComponent('<!DOCTYPE html><html><head><title>Title</title></head><body><h1>Title</h1>Content</body></html>'))})()
This basically opens some text/html content in a new tab/window using a data url.
This technique apparently does not work anymore in Firefox 61.0.1 (haven't tested other versions). Is this a bug or by design?
A particular implementation using a javascript url doesn't appear to work either.
If this is by design, then is there any simple alternative other than opening a new tab and then writing the content afterwards?
Note: I believe this restriction does not apply to plain text content (possibly others).
Partial answer:
javascript:(function(){open('javascript:"'+encodeURIComponent('<!DOCTYPE html><html><head><title>Title</title></head><body><h1>Title</h1>Content</body></html>')+'"')})()
The above is a workaround. encodeURIComponent is useful if either double quotes or single quotes need to be escaped (but not both at the same time)
Using version 4.3.2 of ckeditor.
Our users are looking to use the playing card characters (spade, club, heart, diamond) within the html.
I save the contents to a NVARCHAR(max) field in our database.
After entering the code into the window, then saving it, the system html encodes the character into the
♣
BUT in a later version of the CKEDITOR (4.7.3) the editor is working correctly, and saving the data correctly.
Here is the issue.
Previous developers have created additional buttons, plug-ins and toolbars. When i copy the ckeditor.js into the directory, the additional plugins, and toolbars are not being displayed.
Even just stepping up or down a incremental version of ckeditor the tool bars and buttons are not being shown.
It appears that the ckeditor.js is obfuscated(sp)
Does the ckeditor.js get compiled, or built using a tool or something similar?
please help with what i am missing.
I upgraded the version, and it appear to be working correctly.
I have an issue that is elsewhere on this website, though I don't see a way to add a comment to it, without being asked to "answer" it.
My website was originally created NOT using UTF-8. We are updating them all now. But late, I know.
But now the German site we built, has this issue of the German characters showing the black diamonds.
We cannot add the longer 'code' for each character as they are words typed into products and menu links. So I assume we have to update our database. I have done this setting it to "utf8_germany2_ci".
I use notepad or notepad2 for writing code. It says "ANSI" in the baseline of the window.
I've read that using "cp850" might be better, but I've not heard of it before now.
Happy to supply screenshots and make any alterations.
I'm using Apache XSL-FO to generate a PDF document from an XML using XSLT. In my XSL file I have an fo:block where I bring a URL and simply display it like this:
xsl:value-of select="company_info/website"
My website always contains a valid URL for some company, starting with www.abc.com
It seems like that by default anything with a www is being recognized as a URL and becomes linkable. It does not seem like I can force the link of that company to load in a new window, as it always loads the page in the PDF window and that's not a desirable behavior. I am trying to find a way to disable to URL altogether so that it is not linkable and the only way I'm able to do it tight now is by inserting '-' on both ends of the URL: -www.abc.com- Is there a more elegant way to insert some kind of a special character that maybe is not visible?
This is probably not something that can be fixed from the XSLT/XSL-FO side of things (except by inserting extra characters, as you have done). It is the PDF viewer that interprets certain strings as clickable links.
In Adobe Reader, you can disable automatic recognition of links by unchecking the "Create links from URLs" check box (Preferences dialog: General->Basic tools). Foxit Reader has this option too.
So my problem is relatively simple, I've Googled all over to find a solution but I've yet to find one.
The problem is, I've developed a WYSIWYG plugin for Drupal's WYSIWYG module/framework (not sure if this is relevant). The purpose of the plugin is to allow embedding of video files inside the WYSIWYG content. Our client offers a video uploading/editing API which their customers use to embed files on their pages.
To put it simply, my plugin opens up a pop-up where the user selects one of their videos as fetched from their account at the clients site, the plugin then calls the API and is returned with HTML and JavaScript for embedding the video which is then inserted into the WYSIWYG content.
This works like a charm in Firefox, however I have a few problems with it in Chrome. After debugging back and forth I've noticed that the embedded JavaScript inside the WYSIWYG editor gets escaped (IE, quotes turned into " etc).
This does not happen with Firefox so it's most likely Chrome which is causing it, or perhaps even Webkit?
I've already checked the HTML and JavaScript that gets returned through the Ajax call and it is fine, it's when it gets embedded inside the WYSIWYG it gets escaped.
The WYSIWYG editor I've tested in is TinyMCE by the way.
Adding as an answer for #tobbr to help other SO users:
i solved this by adding the script to a db table instead and then
loading it using drupal_add_js with hook_nodeapi. works better and
solves another IE related problem