I am having some trouble with CKE 4. Where I work they decided to enable the Content security policy sitewide.
So now CKE and custom plugins are not working but they want to continue using the editor until everything will be switched to CKE 5.
I sincerely do not know how to solve this since CSP or is enabled or is not enabled. I know about the hash but is supported only in chrome and edge.
Does anyone already have faced this issue?
I tried to look online but I do not think there are easy options, unless they detect when CKE is going to be used and omit the CSP headers only on that case.
Related
Is it possible to cache specific resources while developing with disable cache option turned on in Chrome Dev Tools?
One might want to cache https://fonts.googleapis.com/css while testing local projects with caching disabled, for example.
You can't using DevTools. The disable cache disables the entire cache possible.
You may star a recent feature request in the Chromium issue tracker asking for just this feature. Please remember that +1, me too, and any other un-constructive comments are not needed. Simply login and click the star beside the issue number in the left sidebar. That will let the developers know others want this functionality as well.
Just upgraded to Windows 10. Switching to SOURCE mode in CKEditor crashes the entire browser and cases to refresh. No way to access source.
Microsoft Edge is a new product, and so far, it has quite a few issues that need ironing out.
CKEditor introduced initial Edge support in version 4.5, but there are quite a few bugs that were reported by us to Microsoft and that need to be fixed on their side.
The issue that you describe was actually reported by us, too, you can find it here: https://connect.microsoft.com/IE/feedback/details/1577449/edge-browser-crashes-when-using-ckeditor-toggling-from-wysiwyg-to-source-mode
Anyone interested in having this fixed is probably most welcome to comment the bug report to highlight it's a show-stopper for many users. Sorry about any inconvenience caused.
As MicroSoft says this problem has been solved after update 1511.
Check this link: Browser crashes when using CKEditor (toggling from WYSIWYG to source mode)
I recently started using the Dojo firebug extension. I had gotten used to it since it had some nice features (letting you see dojo on the widget level). This was good for me because I am in the process of trying to learn dojo so this really let me see how stuff worked together.
My question is, has anyone found any solutions to get the Dojo firebug extension working in Firefox 6 or should I just try downgrading to FF5?
Thanks
UPDATE:
I tried a workaround I found somewhere else. It said to use the Firefox nightly build add-on, and that add-on would allow me to override the version compatibility. I tried that and it still didn't work.
I recommend trying the Add-on Compatibility Reporter extension from Mozilla. This extension (besides letting you report incompatible add-ons) lets you completely disable version checking.
It's a great way to ensure that older extensions still work when Firefox upgrades the browser every week. Now, this assumes that the issue is with version compatibility, and not that the plugin is actually broken! If it's the latter, there's not much else you can do.
(Also, that's an awesome plugin. I'm definitely going to try it out myself here shortly!)
Background Info
I'm currently searching around for ways to add support for older versions of Internet Explorer for an existing project that uses Protovis (and therefore the tag). My searching around has led me to two main places:
http://multimedia.journalism.berkeley.edu/tutorials/protovis-internet-explorer/
Touches on the Chrome Frame plugin as well as SVGweb
https://gitorious.org/protovis/jloves-protovis
Seems to be an integration of Protovis with SVGweb
So far, I've downloaded the examples from each of these and opened them up in IE8 and have had no success whatsoever. The exact version of the IE is 8.0.7600.16385 and is running on a 64 bit Windows 7 Machine, and for the sake of SVGweb, the Flash version installed is 10.2.152.
The question(s)
Since I've had no luck making any of these work, I'm wondering if I'm doing something wrong. Can anyone verify that the examples found in http://multimedia.journalism.berkeley.edu/media/upload/tutorials/protovis/protovis-ie.zip and/or https://gitorious.org/~jlove/protovis/jloves-protovis/commits/master work in IE8? If not, is there any other way (preferrably server side, but if there is a plugin that users can download and install for IE8 that would be okay too) to make protovis work on older IE versions?
Thank you for any help or advice!
I never had any luck with either of those solutions either. However, datamarket.com have recently come up with a drop-in shim available from http://blog.datamarket.com/2011/06/22/protovis-support-internet-explorer-8/ which worked right out of the box for me. The only drawback is that interactive aspects of your visualisation may not work in IE using the shim - I had some drag-select functionality that I had to re-implement with sliders under IE.
im a bit new at extension development, but im about to embark upon a project to build a ffox extension.
Does anyone know if its possbile, with minimal adaption, to make a firefox extension compatible with ie8 as a plugin and if so, are there any caveats i should be aware of?
I guess its just javascript code wrapped around the ffox or ie8 wrapper, but would really appreciate to learn from someone who has experience.
Cheers
Ke
Others may know better than I but I don't think there's any "minimal adaptation" (<- I'm assuming you meant to say "adaptation") way to do this. IE plugins are COM and FF plugins are coded with JavaScript and XUL.