CKEditor: Disable default linking of email ids - ckeditor

I am using CKEditor recent version. Whenever a user types his email ID an anchor link is created. Like abcd#example.com is created in the output. How do I disable this property in CKEditor configuration.
I tried config.forcePasteAsPlainText = true; and it didnt help in this particular case.

Auto Url Detection is an IE feature, and as of IE9 you can disable this.
Prior to IE9, it was not possible to specify IDM_AUTOURLDETECT_MODE from JavaScript, meaning that pages could not disable automatic hyperlinking in ContentEditable areas. A new command constant AutoUrlDetect is supported in IE9, allowing script to disable automatic hyperlinking as follows: document.execCommand("AutoUrlDetect", false, false)
You could try executing this call on the editor's document object.

You can also, before CKeditor creates the output (for example the moment the user clicks on the submit button) search for # in input and replace them with #

Related

CKEditor custom config not working in draft-workspace

I created a custom config file for CKEditor using a yaml-file as suggested and registered it in my extension for my custom elements.
$GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']['custom_rte'] = 'fileadmin/templates/css/custom_rte.yaml';
This works fine as long as I'm in the default workspace.
When I switch to the draft workspace and save an element, the config is lost and I get the default Toolbar, without my custom css and buttons.
Any idea what this could cause?
Typo3 8.7.15
The solution was actually pretty easy.
I had to set the default preset for the CKEditor in the extension, instead of using the custom one and then set that in the Page TSConfig.
So this works (in ext_localconf.php)
$GLOBALS['TYPO3_CONF_VARS']['RTE']['Presets']['default'] = 'fileadmin/templates/css/custom_rte.yaml';
That way the CKEditor always uses my custom yaml-file. No Page TSConfig needed.

Disable CKEditor on Page Load

I am using CKEditor to provide a WYSIWYG for one of the fields I am storing in the database.
There are records marked as deleted and so editing them is forbidden. I managed to disable all the input fields inside my form by adding the disabled attribute on the fieldset element. This approach however doesn't disable CKEditor.
I'm not sure what version this got implemented but on CKEditor 4 using
CKEDITOR.config.readOnly = true;
seems to solve the issue.

firefox addon iframe type

I'm new to firefox and I used JPM to make a firefox addon and submitted it to Mozilla. One reason they gave for rejecting it was the use of iframe elements without a type attribute.
Here are the two situations that an iframe will be loaded.
Whenever a page is loaded a content script will be injected to that page and that content script will insert an iframe that acts as the extension's menu. I set the type attribute using jquery append.
$("body").append("<iframe type='content'></iframe>")
Whenever a user clicks a button appended to a youtube video it will load the video through an iframe and display that video on the page with some additional viewing features. The type attribute is being set using vanilla javascript myIframe.type = 'content'
Is there something I am completely missing or is how I am setting the type attribute correct?

Tablesorter disable pager button not working when using ajax

The disable pager functionality is not working as I would expect when using ajax with tablesorter. The pager controls are disabled but the complete set of rows is not retrieved and shown. When not using ajax, it works fine - ie the complete set of rows is shown.
I notice that clicking on the disable pager button triggers the showAllRows function in the jquery.tablesorter.pager file. Then showAllRows calls pagerArrows if ajax is being used. This last function only seems to manipulate the css for the pager controls and does not re-render the table. Is this working properly for others?
Thanks
This does sound like a problem. I would recommend opening an issue so that it can be tracked and addressed.
I am on a sabbatical at the moment, so if the caretakers of the repository are unable to take care of it, I will look into this issue upon my return. Sorry for the delay.

Lotus Web Form Scroll and Popup issue

I am trying to create a web form in Lotus Notes that is web enabled. So far this has all worked fine, however there are 2 issues.
When Creating a Java Script Alert in the OnLoad Event, it Pops up everytime a user selects a radio button or dropdown option since this reloads the page. Is there any way to make this only for the initial opening of the form?
When a user selects an option, the form reloads and puts that form field on the top which is proving to be very disorrienting for users. Is there a way to have it not scroll on reload?
Thanks in advance!
The best advice would be: use XPages for web development that is "state of the art". If you can't, you have to code a lot of JavaScript to make the form not behave like "havoc".
First of all: the field property "refresh fields on keyword change" is the reason for the jumping / reload.
What does domino do?
All events / formulas that occur when you normally press F9 or use the Option above (that can be field values, input translations, hide whens, etc.) are not "converted" to HTML and javascript but are executed by the server. Therefor each change in a field with the option set submits the form and adds an &Seq=x to the url to keep track of the state. X increments on every reload. Of course this reload causes all events to be triggered again.
For you this means:
Option
disable the option to reload the form after keyword change.
Unfortunately you have to recode every dependency / calculation / hide when with javascript. Using a framework like jquery or dojo this is possible, but a lot of work.
If there IS no dependency then just disable the option...
Option
Live with the "jumping" and let your onload event check for the existance of an URL- parameter called seq... And only if it does not exist, then it is a "real" OnLoad...
Both options are not quite nice and not very easy to code...
That's one reason why IBM started XPages... There all this stuff is already handled by default...

Resources