Well, this is not exactly the right place to post a bug report of the plugin, but posting isn't possible either on plugin's homepage as their automatic comment filter seems to be too intolerant or faulty.
I got this module and plugin working with all the most popular browsers except Firefox 12.
For Firefox compatibility I had to replace these lines of plugin.js:
for (var i=0; i<window.frames.length; i++) {
if(window.frames[i].name == 'iframeMediaEmbed') {
var content = window.frames[i].document.getElementById("embed").value;
}
Simply with this:
var content = window.frames['iframeMediaEmbed'].document.getElementById("embed").value;
After making the fix above, I noticed, that there exists also rewritten plugin.js that is more streamlined than the original version and fixes this issue for Firefox aswell.
Comments
Comment #1
pfournier commentedComment #2
capellicI discovered the same error on Firefox 18 on OS X. I saw that there was a new version of the library. I tried it and then CKeditor disappeared completely. I followed the replacement instructions above and it fixed it.
Comment #3
hongpong commentedThank you for the solution to this situation. I am marking it as postponed as it is not within the Drupal module's purview. The current author's URL seems to be here. http://ckeditor.com/users/frozeman
Comment #4
jibus commentedSame issue on Firefox 40.0.3
The plugin.js from http://jsfiddle.net/redsun/ws9Vh/ of #1 resolves the issue
Comment #5
jibus commentedSet the issue to active
Comment #6
hongpong commentedThank you, I just got the full permissions on this module and might roll that jsfiddle version into the module since it's MIT license. Do you think that is a good idea jibus? I haven't touched the module in quite a while and would like feedback.
Also would be best to get a class on there as requested: #2493897: Set a className to the wrapping div element
(I will post a request here https://www.drupal.org/project/issues/drupal_lwg before adding any MIT license code to the repo here, but I might make another repo on github for it)
Comment #7
pfournier commentedUsually, modules do not include external dependencies.
It might be a good idea to use the libraries module to manage that.
Comment #8
hongpong commentedGood call pfournier, even though the library is small I should take that approach unless there is some compelling reason not to.
Comment #9
jibus commentedI agree also with pfournier.
About the div, i think we should leave it as it is, since the filtered_html doesn't allow div.
Comment #10
hongpong commentedThere are a lot of people that use Full HTML though, or might allow just a class on a div. I think it shouldn't break anything, it would just be stripped if the filter is engaged.