I'm using a pretty bog-standard installation of CKEditor 5, and have noticed that alt-clicking on a Mac is acting differently in ckeditor to a basic textarea.
Textarea:
Right click a word, and it will be selected - 100% of the time.
CKEditor:
Right click a word - it seems a little unpredictable - the only way I can make it work every time is if I place the cursor within the word everytime.
This issue was raised as a user pointed out that the browser spellcheck only works on the second attempt, so not ideal.
I created a video showing the behaviour on the ckeditor examples website - with a textarea just thrown in using devtools - https://www.youtube.com/watch?v=k0pDCdbNZpc
Has anyone come across this before and found a solution at all? Thanks!
edit: confirmed as an issue on GitHub https://github.com/ckeditor/ckeditor5/issues/11898
Related
I have created two CKEditor plugins. Each of them uses an "Iframe Dialog Field", meaning that a dialog box is launched and the contents of that dialog box is a webpage (you can think of the entire dialog box as being like one big iframe).
Each plugin works perfectly on its own. However if I use both plugins in the same CKEditor app, they both end up displaying the same page, rather than two different pages, despite the fact that they point to two different pages. I see no reason why this should be happening. Does anyone know how to prevent this?
To make sure there is no confusion, an "IFrame Dialog Field" is a dialog box whose contents are another webpage.
Documenentation - http://ckeditor.com/addon/iframedialog
[ This is different from using an "IFrame dialog", which I believe is a plugin that lets the user add an iframe to the page.
Documentation - IFrame Dialog: http://ckeditor.com/addon/iframe ]
In terms of usage, when using an IFrame Dialog Field, you specify the url of the page to load in the addIframe() command. Here is an example of using a CKEditor Iframe dialog
https://gist.github.com/garryyao/1170303
Back to my issue - if I use just one of the plugins in my CKEditor, it works perfectly. Each plugin points at a different url, and opens that url as the contents of the dialog box. But, if I use both plugins in my CKEditor, although I see a different icon for each, both end up launching a dialog box which points to the same url. Depending which one I launch first, that is the url both end up opening. It is as if you are only allowed to use one IFrame Dialog Field in CKEditor, and the first one used overwrites all others.
This same question was asked a couple of years ago, with no response on the CKEditor forum. The person who asked the question posted his solution, or rather his workaround, which was to NOT use the IFrame Dialog Field altogether, but to instead use a regular dialog and then put an iframe element within it.
http://ckeditor.com/forums/CKEditor-3.x/multiple-iframedialog-plugins-display-same-dialog
That seems like an OK workaround, but it is a workaround and not a solution. I haven't tried it yet, and don't know what potential issues I will run into if I go down that route. I'd prefer to fix my existing code rather than rewrite the plugins, unless I have no choice.
Any help would be appreciated.
Since I have not found any further information, or received any answers here, I ended up going with the workaround mentioned at the end of my question - I used a regular dialogue box and put a big Iframe within it. This problem doesn't exist with that approach, and It looks pretty much the same as an Iframe dialog box. (Considering the almost total lack of community support with CKEditor customization, I've realized it is better to just adjust your design/concept to do what is more easily accomplished with CKEditor, rather than get CKeditor to do exactly what you want).
I'm really quite new to Joomla and I've encountered a problem. On my homepage the article is showing just fine, but all the other modules (except for the menu bar) disappear when I switch to a smaller screen size. On my other pages the article doesn't even show anymore, just the menu bar. I'm using the purity III template. I have no idea what's going on since the settings in the layout of the template indicate that all modules that are showing on a desktop should also be displayed on a mobile device, and I've found no difference in settings in the articles itself. My site.
Thanks for your help!
It sounds like the responsive design hides them on purpose.
Just from a quick peek at your code using inspect element I can see that the class "slideshow hidden-xs" gets a display:none on smaller screen sizes and all of your main content is wrapped in that element. If all of your content is not supposed to be wrapped in that element (which I'm guessing it's not) you're most likely missing a closing tag on a div or something.
Find the missing closing tag (ie: /div, /a, etc) and it will probably solve your problem.
You can update the latest version of Joomla and check again that some problem is coming or not. I yes then download new theme for your website which is compatible with your theme.
Today, I open my website which use CKEditor.
I encounter a strange behavior. In any page that has CKEditor, jquery click event listener seems to not work.
This is odd. I have try to open the same website in chrome and firefox 32 with no problem.
I even try to visit CKEditor website to make sure that this problem is not caused by my script.
And I can ensure that the problem is occurred exactly as in my website. CKEditor has javascript based menu, if you click "Full featured" link, the element on the left-side should be changed with respective element. But it doesn't response as it should be. (Just for the record, this website also works fine in chrome and firefox 32)
I have also use firebug to find any helping-error-message, but I can't find any error message there.
I am sure this must be firefox's bug. Hopefully they will fix this in firefox 34.
However, does anybody experience the same problem? Is there any workaround for this?
UPDATE : Seems that this problem is caused by plugin (firePHP or fireQuery). Look at the comments for more information.
Ok this may be a vague question but I have an issue recognizing a webelement in one module (tab) but works completely fine in another tab. This is the same webelement. Everything seems to be same. It's the same form on the gui side with same properties and values.
Now this is another weird part, I can add one to the object repository but when I go to the other tab and try the same qtp becomes extremely slow. The + sign for adding it to the repository appears but when I click it, it gives me a message saying this object cannot be added to the repository.
The Web app uses extJS if that matters and this is a high level webelement that has a constant html id. I'm just puzzled as to why it works in one module but not the other.
There are also some subtabs where you can click on this form. Those work fine but when it comes to capturing this element the issue persists.
Any hypothesis as to why this is happening?
Okay it looks like it works when I took off the visible identification and just identifying it by the html id. I still don't get why taking the visible made a diff but it works.
We're having a very peculiar problem with a site that is using mod-pagespeed. Here's the link in question -
http://www.microsemi.com/applications/
If you try to expand one of the sections by clicking on the '+' sign you need to click twice to open.
However if you disable pagespeed using http://www.microsemi.com/applications/?ModPagespeed=off
The link works correctly.
What is the best way to debug this ? Is is possible to selectively disable javascripts from being processed by mod-pagespeed ?
I'd start first of all with looking at the errors that are thrown up on the page in chrome console:
Uncaught ReferenceError: Tips is not defined www.microsemi.com:43
Failed to load resource http://www.microsemi.com/media/system/js/mootools-more.js.pagespeed.ce.BqakF5Rbjl.js
These are presumably related as the errors vanish on the second link without page-speed. I'd assume the second one must be the reason why two clicks is needed - for some reason there is a javascript file missing using mod_pagespeed - also presumably containing jQuery UI.
I should probably add that it says here mod-pagespeed only seems to be of use for badly written sites. Joomla is well written so as long as you have well functioning extensions there should be negligible difference on your site!