We are migrating CKEditor issue tracking to GitHub. Please, use GitHub to report any new issues.

The former tracking system (this website) will still be available in the read-only mode. All issues reported in the past will still be available publicly and can be referenced.

Important: we decided not to transfer all the tickets to GitHub, as many of them are not reproducible anymore or simply no longer requested by the community.
If the issue you are interested in, can be still reproduced in the latest version of CKEditor, feel free to report it again on GitHub.
At the same time please note that issues reported on this website are still taken into consideration when picking up candidates for next milestones.

To report a new issue, go to https://github.com/ckeditor/ckeditor-dev/issues and follow the instructions in the issue template.

Context Navigation

Changes between Version 1 and Version 2 of Ticket #7784, comment 9

Timestamp:: Jun 23, 2011, 11:09:42 AM (13 years ago)
Author:: ron
Comment:

Legend:

: Unmodified
: Added
: Removed
: Modified

Ticket #7784, comment 9

-                      v1
+                      v2
 My solution was this...
+                        for(h=0;h<c.styleSheets.length;h++){
+                                var i=c.styleSheets[h],j=i.ownerNode| |i.owningElement;
+                                if(j.getAttribute('data-cke-temp')){
+                                        continue;
+                                }
+                                if(i.href&&i.href.substr(0,9)=='chrome://'){
+                                        continue;
+                                }
                                 if(i.href !== null){
 …
+                                        }
+                                }
+                        }
 The error was being produced when the instance first loaded. After that the stylesheet was loaded the combo would be populated when checked.