Custom Query
Results (2201 - 2300 of 2591)
Ticket | Summary | Status | Owner | Type | Priority | Milestone |
---|---|---|---|---|---|---|
#3371 | Spring based Connector servlet | confirmed | New Feature | Normal | ||
Description |
Attached is a patch which has a new spring based connector servlet project. It allows the Connector to be a Spring managed bean which is useful in Spring projects. For example if the connector is used to write to a database it will be able to use the Spring transaction manager or Spring events could be issued when an upload/download occurs for files. I`ve also updated the java-demo project so it uses the new servlet. I`ve commented out the original ConnectorServlet in the web.xml I had to change the Dispatcher slightly so a Connector can be passed into it. I also had to make the dispatcher member variable in the ConnectorServlet protected as the new SpringConnectorServlet derives from ConnectorServlet. |
|||||
#14239 | Spurious nodes added to document when toggling source view control when certain ACF rules applied | confirmed | Bug | Normal | ||
Description |
Steps to reproduce
CKEDITOR.config.extraAllowedContent = 'summary';
Expected resultI do not expect to see random <p> </p> added to the document. Actual result<p> </p> nodes are rapidly added to the document, corrupting it. Other details (browser, OS, CKEditor version, installed plugins)A demo of this bug is present at the following URL: https://jsfiddle.net/kamelkev/hqLbhzxz/1/ I have observed this issue with current Firefox (42), current Safari (9.0.1) and current Chrome (47.0.2526.80). I have observed this issue with the most recent release (4.5.5), but replicated it with older versions as well. Note that the issue does not appear to manifest itself if you use the ENTER_BR entermode. Note the issue does not appear if you disable auto-paragraphing. Note the issue does not appear if you apply the fix from the following stackoverflow article: http://stackoverflow.com/questions/24283528/line-break-and-paragraph-has-doubled-itself-every-time-i-save-the-document-ckedi |
|||||
#667 | [SS] Combination of a link and a style | new | Bug | Normal | ||
Description |
Following situation: Prerequisites
<Style name="Fat link" element="a"> <Attribute name="class" value="aBold" /> </Style>
IE behavior crashes with Unknown runtime error Line 28 in fckstyledef_ie.js > e.innerHTML = oRange.htmlText ; May be it is a IE bug... FF behaviour Firefox has 2 conditions
New document -> New <a class="aBold"><a href="bala.ccc/">document</a></a><a href="bala.ccc/" />
In both browsers if the style choise is done first, there are no problems. This problem is not as big in new documents as in old stuff where hyperlinks exist and have to be "re-styled" or modified. Best regards SelfMan
Moved from SF: |
|||||
#8402 | SSI-style HTML comments inside href attributes are broken when Source button is clicked | confirmed | Bug | Normal | ||
Description |
SSI-style HTML comments such as <!--#echo var='DOCUMENT_NAME' --> become broken when the Source button is clicked. Example: Using the CKEditor demo site, click the Source button and add that comment to the first link: <a href="http://en.wikipedia.org/wiki/Fairy_tale/<!--#echo var='DOCUMENT_NAME' -->" title="Fairy tale">fairy tale</a> Then click Source to view the content in the normal editor mode. When you click Source again, the link becomes this: <a href="http://en.wikipedia.org/wiki/Fairy_tale/{C}<!--#echo var='DOCUMENT_NAME' -->" title="Fairy tale">fairy tale</a> Note the {C} that has been added. In fact, every time the source is viewed, another {C} is added: <a href="http://en.wikipedia.org/wiki/Fairy_tale/{C}{C}<!--#echo var='DOCUMENT_NAME' -->" title="Fairy tale">fairy tale</a> <a href="http://en.wikipedia.org/wiki/Fairy_tale/{C}{C}{C}<!--#echo var='DOCUMENT_NAME' -->" title="Fairy tale">fairy tale</a> and so on. |
|||||
#8114 | stack overflow at line: 26 old staff in Ckeditor | confirmed | Bug | Normal | ||
Description |
I send the content of a form to CKEDITOR that has tags like this: <dl> <dt><dd>text<dd><dt> <dt><dd>text<dd><dt> <dt><dd>text<dd><dt> </dl> and as you see the <dt> tags are not closed as they should. The ckeditor cant show the content of the form mailed to this editor and make a stack overflow at line: 26. Is there any way to fix it? Regards |
|||||
#5535 | Stack overlow in IE6 when pasting strange HTML | confirmed | Bug | Normal | ||
Description |
When pasting HTML that contains lots of nested tags, IE6 throws an error: "stack overflow at line: 27". Steps to reproduce
|
|||||
#16858 | Standard distribution of upload file plugin code differs from referenced source. | confirmed | Task | Normal | ||
Description |
The standard distribution of the uploadfile plugin requires the link plugin. However, the Source code made available through the Add-on section of the website indicates that link is not required. My preference would be to not require the link plugin - it isn't actually required to perform the upload. Removing it would also better support those of us that integrate our own and remove the link plugin. That said, the request is to make these two source paths consistent so there isn't confusion about what the plugin requires. Std Dist: https://github.com/ckeditor/ckeditor-releases/blob/master/plugins/uploadfile/plugin.js Source: https://github.com/ckeditor/ckeditor-plugin-uploadfile/blob/t/12541/plugin.js |
|||||
#16854 | startupFocus: false doesn't work in IE 11 | new | Bug | Normal | ||
Description |
Steps to reproduceThe CKEditor is used as a component in a react interface with possibility to add new groups of form elements for user input. Whenever the group of form elements consists of at least one RTE, this element is focused in the interface although there are other form elements above it. The configuration for startupFocus is set on false. This works without problems in Firefox or Chrome, but has no effect on its behaviour in IE 11. Expected resultNo scroll event to focus the CKEditor when adding a group of several form elements. Actual resultCKEditor is focused. Other details (browser, OS, CKEditor version, installed plugins)
|
|||||
#11625 | Start using different hashes instead of timestamp for loading resources (via getUrl) | review | New Feature | Normal | ||
Description |
Using timestamp to mark unique builds worked fine in the past where we released packages once per ~month. Now, when lots of users try different builds, overwriting the same location and then scratching their heads why something does not work, we need to do something different. See for example http://ckeditor.com/forums/CKEditor/Bug-with-custom-builder-and-language-selection, there were more issues reported like this.
My suggestion is to go with assigning a
Using 6-characters long hash that consists of small letters + numbers, gives ~1 838 265 625 ( |
|||||
#10947 | Status bar path not selecting 'caption' and 'thead' in table | confirmed | Bug | Normal | ||
Description |
See the below link |
|||||
#9988 | Stop using <a> for everything. | confirmed | Task | Low | ||
Description |
What's reason to use <a> element with javascript: pseudo hrefs? I think we should use <button>'s for buttons. Why not? Or at least <span>'s. Same with context menus. |
|||||
#3368 | Strange behavior when placed inside dynamically-created elements | confirmed | Bug | Normal | ||
Description |
The following code: var div = document.createElement('div'); var div2 = document.createElement('div'); var editor = CKEDITOR.appendTo( div ); document.getElementById('tests').appendChild(div); var button = document.createElement('button'); button.innerHTML = 'click me'; button.onclick = function(){ editor.destroy(); editor = CKEDITOR.appendTo( div2 ); document.getElementById('tests').appendChild(div2); }; document.getElementById('buttons').appendChild(button); Fails with: holderElement is null as soon as one clicks the button. I noticed this since I'm using CKeditor to implement some kind of "click & edit" rich text field, and I'm creating the containing div dynamically, each time the user clicks the field. I could solve this by re-using the same div each time the field switches to edit mode, but that would be hacky, and I don't think CKeditor should fail here (correct me if I'm wrong, please). Regards, Pedro |
|||||
#8334 | Strange behaviour, missing line | confirmed | Bug | Normal | ||
Description |
when i do the following stpes, one of lines will be missed.
there are 2 lines instead of 3. . one of the line missed. . . i am want to know what kind of logic do ckeditor deal with <br> and <p> so that i can do some work around. |
|||||
#10404 | Strange insertHTML behaviour with FF 20.0.1 after selectRanges and hide/show | confirmed | Bug | Normal | ||
Description |
Firefox Version: 20.0.1 I am not sure if this is a ckeditor issue or a FF bug. But since I wasn't able to reproduce it with a plain contentEditable div I am reporting it here first. Reproducible on the Demo Page: Copy/execute the code line by line, don't execute the block as a whole. Apperently there is a timing component to this bug, that I wasn't able to reproduce it with setTimeout. var cke = CKEDITOR.instances.editor1; var r = cke.getSelection().getRanges(); jQuery('#demo-standard').hide(); jQuery('#demo-standard').show(); cke.getSelection().selectRanges(r); cke.insertHtml('<img src="http://b.cksource.com/a/1/img/sample.jpg" />'); After that, if you doubleclick the inserted img. A phantom image appears that is not inside the Browser DOM and dissapears when the text is edited. I tested this against release/4.1.x 3cb9cc24ed187a8ad29b810798f3427cc45a6fcf This Code is my attempt at a workaround for Issue #10402. Any tips on how to workaround those two problems is appreciated. |
|||||
#10305 | Strange jumps to the top in Firefox upon dialog closing (testcase included) | confirmed | Bug | Normal | ||
Description |
Affects Firefox 20.0 (the latest version atm). Does not affect WebKit-based browsers. Reproducable: Always. Steps to reproduce:
What actually happens: The CKEditor viewport is instantly scrolled to top (jumps). What should happen: The viewport should remain as it is. If the height is changed after editing the image, the top border of the visible area should remain the same, and the viewport should extend to the bottom (as it does when everything is fine). Additional notes: Clicking the last image is not requred, you can use either one. This depends on if the text at the left (the «Foo» lines) is in the viewport. If you can still see the text (not scrolled down or the viewport is large enough), then the bug won't trigger. |
|||||
#6771 | Strange <span> refactoring | review | Bug | Normal | ||
Description |
insertHtml('<span><br><br><span>foo</span></span>') |
|||||
#16903 | STRICT MIME TYPE ERROR | new | Bug | Normal | ||
Description |
Steps to reproduce
Expected resultCkeditor shown, no errors Actual resultMIME TYPE strict error, Refused to execute script from 'https://www.XXX.XX/forum/general-discussion/config.js?t=H0CG' because its MIME type ('text/html') is not executable, and strict MIME type Other details (browser, OS, CKEditor version, installed plugins)Chrome browser Ckeditor 4.6 cPanel |
|||||
#10003 | Strike through button doesnt not correctly | confirmed | Bug | Normal | ||
Description |
Strike through doesn't work for first time for the steps given below: Way to reproduce:
1) Enter some text and select it. Click strike through |
|||||
#9756 | Strikethrough splits text in Opera | confirmed | Bug | Normal | ||
Description |
If strikethrough is pressed without any text being selected it splits the text into two lines in Opera. Steps to reproduce:
Browser: Opera 12.11 (Linux) |
|||||
#7788 | Strike through with sub/sup for newly entered text - strike line is not crossing the text | confirmed | Bug | Normal | ||
Description |
EnvironmentOpera 11.10 TC 1
Actual resultStrikethrough line is placed above entered text TC 2
Actual resultStrikethrough line is placed below entered text Expected result for TC1 and TC2
In other browsers above cases are working fine |
|||||
#2728 | String.prototype.Trim should also trim unicode ideographic space | confirmed | Bug | Normal | ||
Description |
String.prototype.Trim (defined in fckjscoreextensions.js) should also remove the Unicode "Ideographic Space" (U+3000), which is used in Japanese. String.prototype.Trim = function() { // We are not using \s because we don't want "non-breaking spaces to be caught". return this.replace( /(^[ \t\n\r\u3000]*)|([ \t\n\r\u3000]*$)/g, '' ) ; } String.prototype.LTrim = function() { // We are not using \s because we don't want "non-breaking spaces to be caught". return this.replace( /^[ \t\n\r\u3000]*/g, '' ) ; } String.prototype.RTrim = function() { // We are not using \s because we don't want "non-breaking spaces to be caught". return this.replace( /[ \t\n\r\u3000]*$/g, '' ) ; } |
|||||
#8426 | Strings for specialchar plugin added directly to editor.lang instead of editor.lang.specialChar | confirmed | Bug | Normal | ||
Description |
The strings for the special characters dialog are available directly on the editor.lang object when the editor is loaded in a new language. They should be inside the editor.lang.specialChar object. To Reproduce:
availableLangs : { en:1, fr:1 },
Problem: All the strings for the specialchars plugin are now available directly on the editor.lang object. Note that these are the strings in English. When the special characters dialog is opened again, the editor.lang.specialChar object is correctly updated with the pseudo French strings. specialchar\plugin.js does extend the editor.lang.specialChar object with the string values. CKEDITOR.tools.extend( editor.lang.specialChar, plugin.langEntries[ langCode ] ); However the CKEDITOR.plugins.load function in core\editor.js always extends the editor.lang object. CKEDITOR.tools.extend( editor.lang, plugin.langEntries[ lang ] ); This works correctly for the a11yhelp plugin because the strings in a11yhelp\lang\xx.js are specified within the accessibilityHelp group. Perhaps the special characters lang files also need to group the strings like this? |
|||||
#13250 | Style attribute type gets corrupted when editing source in IE 8 | confirmed | Bug | Normal | ||
Description |
We want to use CKEditor to provide a full html document editor, and we want to use the <style> element in the <head> section. We found that when using IE 8, the attribute type="text/css" in the <style> element is changed to type="text" when switching from source to visual editor then switch back to source view. I am using the nightly build in the following steps, but I have used the master and the major branch on github and they all have the same problem. Here are the step I used to reproduce this bug :
I have tried to fix the bug by myself, but after 2 hours digging into the parser in the javascript console I surrender. Everything seems fine (the source is well parsed), but at some point when the DOM is inserted the content is modified. If you have hints about how I should help to fix the problem by myself feel free to point me, or if you have any workaround. I have tried to use bender but was stuck by a strange error in testbuilder.js on master branch. Anyway it was not related to the debugging of the code. |
|||||
#10153 | Style combo update issue when inline editor programmatically created and focused | confirmed | Bug | Normal | ||
Description |
When programmatically creating an inline editor and giving it focus, the style combo doesn't reflect the selected style of the cursor. Worse, in Chrome, when you move the cursor/selection while in the same HTML element, the combo still doesn't update. It's not until you switch to a new element that the combo box starts updating. May be easier to understand with this repro. Using the HTML/JS below, do the following in Chrome (I also attached a zip file):
I've been unable to find any workaround for this bug. Repro HTML: <html>
</html> Repro config.js: CKEDITOR.editorConfig = function( config ) {
}; |
|||||
#6415 | Style defined in stylecombo plugin with "pre" element ignores class property in Internet Explorer when applied without selecting text | confirmed | Bug | Normal | ||
Description |
Steps to reproduce:
CKEDITOR.config.stylesCombo_stylesSet = 'wiki_styles'; CKEDITOR.addStylesSet('wiki_styles', [ { name: 'Code', element: 'pre', attributes: { 'class': 'Code'} } ]);
|
|||||
#5026 | Style detection/removal incorrect in FireFox | confirmed | Bug | Normal | ||
Description |
Recreate BugUse Firefox (I tested on both Windows FF 3.5.7 and Linux FF 3.5.5) and the online demo and perform the following steps. Setup
Test 1
This inconsistency is confusing my users and is likely related to the odd behave I will describe next. Test 2
Unless you delete both |
|||||
#13206 | Style is not visible if it uses multiple classes | review | Bug | Normal | ||
Description |
When the classes are not sorted alphabetically (in the string), it will not be made available because it is deemed not "applicable", because it does not pass the test in objectCompare(element.attributes,clone.attributes). Example: a style in stylesset with the following definition: {name:'Multi Class', element:'p', attributes:{class:'c b a'}} Will not be selectable from the combo because when a clone is created from the element and then compared, the compared class-string is ordered alphabetically 'a b c'; 1652 core/filter.js/processElement/updateElement loops through all possible classnames and then sorts them on line 1658 classesArr.sort().join( ' ' ); 140 stylescombo/plugin.js style.checkApplicable() 366 core/style.js checkApplicable/filter.check() 744 core/filter.js CKEDITOR.toosl.objectCompare() thus the object comparison fails... |
|||||
#4902 | <style> output formatting incorrect | confirmed | Bug | Normal | ||
Description |
Style tag content should be left as untouched. Reproducing Procedures
|
|||||
#8045 | Style override only works for attributes | confirmed | Bug | Normal | ||
Description |
|
|||||
#4523 | Style plugin should allow refreshing of data | confirmed | New Feature | Normal | ||
Description |
Custom plugins and extensions are able to extend the list of loaded styles in the styles plugin. Unfortunately the styles plugin does not reflect dynamic changes to its list of styles and requires a reload of the whole editor to reflect the new options. Ideally the editor should provide a way for any plugin to be reloaded without requiring the whole editor to be reloaded. Alternatively, a simpler approach to this problem would be to allow just the styles plugin to reload its data dynamically, through some additional API. |
|||||
#12905 | Style removal context menu | confirmed | New Feature | Normal | ||
Description |
As you know, one of the worst (notorious) problems about WYSIWYG editors is the style mess made when pasting, or when styling using a pure visual approach. You make a number of efforts to mitigate this: the advanced content filter, paste from word, I think other internal filters, and sensible decisions regarding how to merge and remove HTML nodes. This is all good, but it does not solve the problem well enough in my opinion, especially for the case where users are pasting into an unfiltered editor (unfiltered due to necessary support for arbitrary markup). I suggest you extend the "Remove Format" plugin to have a context menu. When you right-click at any point in the document it has an item on the context menu to remove any of the inline styles defined above that point. For example, you paste something in and it has got a line-height there (because the browser extracted it from some CSS class when you did the original 'copy' op). The user can right click, see it there, and remove it. This stops them needing to remove it manually from the HTML view, which frankly is scary when a lot of inline styles are defined. It would be good also to be able to choose to remove a style globally (i.e. remove all line-height defined for any node). Please consider this. I think it would be a really big improvement to CKEditor. |
|||||
#6331 | Styles applied to all children elements | confirmed | Bug | Normal | ||
Description |
paste this in the editor : <ul> <li> line 1</li> <li> line 2</li> <li> line 3</li> </ul> then apply a style (from the Styles list) to the UL. The style is then applied to all LI children elements... On my site, applying a style ({ name : 'Slider content' , element : 'div',attributes : { 'class' : 'slider_content' }}) to the UL gives this : <ul> <li> <div class="myClass">line 1</div></li> <li> <div class="myClass">line 2</div></li> <li> <div class="myClass">line 3</div></li> </ul> instead of : <div class="myClass"> <ul> <li> line 1</li> <li> line 2</li> <li> line 3</li> </ul> </div> hoping I am not mistaking on this issue... |
|||||
#9174 | Styles applied to inner table are also applied to outer cell. | confirmed | Bug | Normal | ||
Description |
I have found it when checking #9154. To reproduce:
Result: Styles are applied to outer cell as well. See video for more details. Problem has been reproducible in all browsers from CKEditor 3.6.1 rev. [6918]. |
|||||
#11762 | Styles are not applied in Internet Explorer if backspace is the last key pressed | confirmed | Bug | Normal | ||
Description |
Steps to Reproduce
Expected result ...to step onto the moon... Actual result ...to step onto the moon... This happens with bold, italic, and underline and occurs with both the keyboard shortcuts and the toolbar buttons. It also occurs if you use multiple backspace presses or highlight the text you want to remove and press backspace once. Browser I can reproduce this on Internet Explorer 9, 10, and 11, it does occur on Internet Explorer 8 or Chrome/Firefox |
|||||
#5192 | Styles are not "eating" overrides partially selected | confirmed | Bug | Normal | ||
Description |
<p>This is <b>some sample</b> text.</p>
Current results: <p><strong>This is </strong><b><strong>some</strong> sample</b> text.</p> Expected results: <p><strong>This is some</strong><b> sample</b> text.</p> |
|||||
#5980 | Styles: combine classes and allow wildcards | confirmed | New Feature | Normal | ||
Description |
Currently, styles can be like this:
]); Problem 1: it is not possible to apply both classes. When a class is applied, the other is removed... Problem 2: when applying myP1 or myP2 to a H2, H2 will be turned into a P. I would like something like this: [
]);
Style myBlock1 could be applied to any block without changing its tag. |
|||||
#16662 | Stylescombo not updated after applying/removing styles to widget. | confirmed | Bug | Normal | ||
Description |
Steps to reproduce
Expected resultStyles combo is updated immediately, showing that no styles are selected for the current selection (widget). Actual resultStyles combo is updated only after changing selection (or applying/removing) different style. Other details (browser, OS, CKEditor version, installed plugins)Tested on Chrome with CKEditor 4.5.11. |
|||||
#3589 | StylesCombo plugin: no option to load from XML file | confirmed | New Feature | Normal | ||
Description |
Like #3588, all the same reasons apply here. People won't like to have to rebuild their xml files into js. |
|||||
#6948 | Styles combo should more accurately reflect the selection | pending | Bug | Normal | ||
Description |
Use the following styles: { name : 'Red Title' , element : 'h3', styles : { 'color' : 'Red' } }, { name : 'Red title with blue background' , element : 'h3', styles : { 'color' : 'Red', 'background-color' : 'Blue' } } And the following content (place the caret somewhere inside the <h3>: <h3 style="color: red; background-color: blue;"> This is some <strong>sample text</strong>. You are using <a href="http://ckeditor.com/">CKEditor</a>.</h3> Open the styles combo. Both "Red title" and "Red title with blue background" are marked as focused, while only "red title" is presented in the combo label. IMO the label should read "Red title with blue background". |
|||||
#13833 | Styles dropdown doesn't work correctly for tables with border=0 | assigned | Bug | Nice to have (we want to work on it) | ||
Description |
Steps to reproduce
CKEDITOR.config.allowedContent = true; CKEDITOR.stylesSet.add( 'my_styles', [ // Block-level styles { name: 'Nice table', element: 'table', attributes: { 'class': 'MyTable' } } ] ); CKEDITOR.config.stylesSet = 'my_styles';
.MyTable { border-collapse:collapse; border:1px solid blue; background-color: #00DD00; } .MyTable td, .MyTable th{ border:1px solid blue; padding: 5px 1em; }
Expected resultIn both tables the Style should be shown as "Nice table" Actual resultOnly works correctly in the second one. The first one has the "cke_show_border" class that CKEditor adds automatically and the Styles system doesn't ignore it. Once you click then it's applied and then it works correctly until you reload the content. Other details (browser, OS, CKEditor version, installed plugins)This has been failing for eons, all browsers demo at http://jsfiddle.net/8jcyf9aa/ |
|||||
#11755 | Styles dropdown not updated after object style change | confirmed | Bug | Normal | ||
Description |
Reproduced on master and major. Checked Firefox and Chrome. |
|||||
#8406 | StyleSheetParser and Fullpage | confirmed | New Feature | Normal | ||
Description |
Currently if FullPage=true then no style sheets are loaded via ContentsCss and hence the styles drop down isn't populated with the styles available for the page. Ideally the stylesheetparser should load all the external styles sheets referenced in the html if fullpage=true |
|||||
#8832 | Stylesheet parser error if file not on cache | review | Bug | Normal | ||
Description |
#7784 didn't fix the problem correctly Reproduction steps:
Proposed solution: Revert [6867] and use http://dev.ckeditor.com/attachment/ticket/7784/7784_2.patch as it wasn't rejected because it failed but instead based on coding style. Or rewrite it anyway that you like and test that now it's correctly fixed. |
|||||
#12290 | Stylesheetparser in dialog | new | New Feature | Normal | ||
Description |
The stylesheetparser is a great feature. Why it is not available in dialog windows? There is a text input for class names of css, but selecting a class would be easier :-) |
|||||
#7810 | [stylesheetparser] Newly inputted styles don't load | confirmed | New Feature | Normal | ||
Description |
|
|||||
#6157 | Styles not selected correctly in the Combobox | confirmed | Bug | Normal | ||
Description |
With CKEditor v3.4b, Windows 7, IE8 or FF3.6 or Chrome 5. Suppose you use the following styleset { name : 'normal', element : 'p' }, { name : 'normal/red', element : 'p' , attributes: { "class": "red" }} Select the "normal/red" style with the help of the combobox. After that move the cursor away, and then click on the previously modified paragraph again. Now the combobox will select the "normal" and not the "normal/red". It seems as if CKEditor selects the first style that matches the HTML element, not regarding the class name. |
|||||
#12684 | Styles removed when cursor is placed at the beginning of a new line | confirmed | Bug | Normal | ||
Description |
Reproduced on demo and nightly build on IE11 on Windows 8.1 Steps to reproduce:
Behaviour: Expected: The text styling on the new line should be the same as that on the previous line Actual: The style has reset to the editor's default |
|||||
#12019 | Styles' states and values when block widget is selected | confirmed | Bug | Normal | ||
Description |
All these behaviours come from a decision we made while working on widget system. We decided that styles will be applicable to block widgets, because they may contain nested editables in which these styles may be applicable, even if they are not applicable to the widget itself (and besides widget styles they never are). This reasoning definitely makes sense - if I have 3 nested editables inside a widget and I want to make all text inside them bold I can focus widget and apply bold. Alternatively, I would have to apply bold three times. To make all this work we needed to modify style system so it traverse non-editable fragments of content, finds nested editables, retrieves their filter instances and asks them whether styles is allowed inside. This part works great. Unfortunately, all the rest is a mess. Problems are caused by inability to correctly set style's command state and value. See the following scenarios.
And I'm sure that there are move lovely cases like these. Therefore, I don't see other option than disabling styles when block widget is focused. Only widgets styles should be active.
Note that this won't change the behaviour of applying style to a selection containing some content outside a widget and a widget (e.g. bolding after doing |
|||||
#5322 | Styles support in the image dialog | confirmed | New Feature | Normal | ||
Description |
I can confirm that the new version fixes the img align= problem. Would it be possible/difficult to add support for replacing the style= with a CSS class for more consistent design (similar to the justifyClasses and indentClasses)? Maybe call it imageAlignClasses... |
|||||
#12633 | Styles system creates two identical subsequent inline elements | confirmed | Bug | Normal | ||
Description |
Reproduced on Safari, Chrome and Firefox. I haven't checked IE.
Result: |
|||||
#608 | Styles XML file support for element="*" | confirmed | New Feature | Normal | ||
Description |
I would like to suggest building support for an <any> element that will apply to any element (equivalent to a ".sample" in the stylesheet which can be applied to anything). for people who don't know what i'm talking about take a look at /FCKeditor_2.0rc2/_docs/contents/006.html in the latest release. So for example - instead of this: <Styles> <Style name="Bold Red" element="span"> <Attribute name="style" value="font-weight: bold; color: Red;" /> </Style> I would like to be able to do this: <Styles> <Style name="Bold Red" element="*"> <Attribute name="style" value="font-weight: bold; color: Red;" /> </Style> I think this would go a long way in helping not to confuse non power-users who will not understand that they cannot find the style "Bold Red" when they have a table cell selected for example when all they want to do is get the text Red. Also I think when a user selects an entire paragraph, then the p tag should get the class assigned as opposed to nesting a span tag inside the p tag. And when the user selects the same paragraph again (because it unintuitively gets unselected after applying a style) and applies a different style, the previous style should get *overwritten* instead of having the new style nested within the old one. It makes for cleaner html and will go along way in reducing html clutter.
Moved from SF: |
|||||
#7754 | Style tag removed by undo command on Internet Explorer (Ctrl + z, or button) | confirmed | Bug | Normal | ||
Description |
Enter in source mode : <style type="text/css"> body { font-size: 14pt; } </style> Back to wysiwyg mode, enter a letter. Finally, do an undo command, and see the source : the style tag dissappeared. |
|||||
#6603 | Styling tags should be detached from the document when removing them from collapsed selections | confirmed | Bug | Normal | ||
Description |
Note that the bold icon is highlighted.
|
|||||
#7704 | Submenu shown on top of a parent menu may block mouse navigation | confirmed | Bug | Normal | ||
Description |
Perhaps this is the same problem as described in comment 15 to the ticket #4594 It only concerns mouse navigation (and so doesn't apply to the keyboard navigation). Please see the image attached and see how the submenu is placed. There is no way to navigate down the main context menu! (well ok, actually there is, but could be quite challenging what should not be the case). I'd like to propose a little patch that deals with it. The simple solution is to move the submenu a few pixels (e.g. 5) to the left (or right in case of rtl lang). In fact that's just a couple of keystrokes :) In file http://svn.ckeditor.com/CKEditor/trunk/_source/plugins/floatpanel/plugin.js change line 255 from left += ( panelSize.width * ( rtl ? 1 : -1 ) ); to left += ( ( panelSize.width + 5) * ( rtl ? 1 : -1 ) ); |
|||||
#1946 | Subsequently creating same folder is responded with error code 0 | confirmed | Bug | Normal | ||
Description |
Running several times http://www.fckeditor.net/fckeditor/editor/filemanager/connectors/php/connector.php?Command=CreateFolder&Type=Image&CurrentFolder=/&NewFolderName=Mika Results always in: <Connector command="CreateFolder" resourceType="Image"> <CurrentFolder path="/" url="/_userfiles/image/"/> <Error number="0" originalDescription=""/> </Connector> Instead of Error number="101" on the 2nd request |
|||||
#12768 | Suggested Modification to jQuery Adaptor to better support jQuery UI | confirmed | Bug | Normal | ||
Description |
When using jQuery UI, there are sometimes issues when CKEditor is instantiated inside a jQuery UI modal dialog. Typically, the CKEditor dialogs become read-only. This is explained here: http://bugs.jqueryui.com/ticket/9087 It would be very helpful if jQuery UI was detected in the jQuery Adaptor (typeof jQuery.ui != 'undefined') and the fix for CKEditor instances in modal dialogs (from the above ticket reference) was executed in that case. I do not expect the JQuery UI developers to implement something specific for CKEditor, so I am hoping that you may be open to adding some variation of this in the jQuery adaptor. |
|||||
#1571 | Suggestion for Find / Replace dialog of v2.5 | confirmed | New Feature | Normal | ||
Description |
Usefulness of the "Replace" tab of the Find/Replace dialog is greatly diminished without a "Find Next" button. To be selective about search and replace requires both tabs with their separate search fields. (You must enter what you're looking for twice) Perhaps I'm missing something, but I think the find / replace tabs could be combined in a dialog with no tabs while being more useful. If the "Find Next" button was added to the replace tab, it could concurrently serve all Find / Replace purpose as a simpler, more intuitive and easier to use tab-less dialog. (e.g. Like the "Edit | Replace..." dialog of Notepad.) Up / down radio buttons could also have significant value if this dialog must be modal, unlike being modeless with Notepad. (or like an always on top floating dialog of the kind I see targeted for v2.6) BTW: Replace tab isn't selected (at least in IE7) on pressing the 'Replace' toolbar button, but the above suggestion would make this irrelevant. |
|||||
#12936 | suggestion for translation - pt-br | confirmed | Bug | Normal | ||
Description |
When you create a table, I can click the right button and open a menu to edit the table. When I click on "cell" have the option "Insert cell before" and "after entering cell". These sentences are wrong in Portuguese, is written ("inserir célula a esquerda" and "inserir célula a direita") and the right would be ("inserir célula antes" and "inserir célula depois"). |
|||||
#2848 | suggestion: make hidden element actually hide in IE too, x-browser behavior | confirmed | New Feature | Normal | ||
Description |
I think it's a good idea to make the behavior of hidden element the same in all browsers. This actually is doable in IE so I have found after lots of searching: Setting FCK.EditorDocument.execCommand('RespectVisibilityInDesign', true, null); makes display:none and visibility:hidden to be respected in editable documents (contentEditable=true). (Setting the second parameter to false instead of true will disrespect visibility, the default behavior of IE; and setting it to null will toggle the option.) See http://msdn.microsoft.com/en-us/library/aa770023(VS.85).aspx (IDM_RESPECTVISIBILITY_INDESIGN) |
|||||
#8584 | Support Content Security Policy | confirmed | New Feature | Normal | ||
Description |
Content Security Policy is a W3D draft aiming to prevent the exploitation of XSS vulnerabilities. It prevents the execution of JavaScript that is directly embedded into HTML code via an inline script element, on-attributes and javascript:-urls. Only external javascript files from a whitelisted domain are executed. CSP is supported by Firefox since version 4.0 and by the current development versions of webkit. Event the Internet Explorer 10 preview has basic support for CSP. The main usecsae of CKEditor is to allow users to edit HTML code, which causes a non zero risk of XSS vulnerabilities in either CKEditor itself or the surrounding website. CSP support would be very helpful to mitigate these risks. Steps to reproduce
Expected Result CKEditor should work, assuming that it was installed on the same domain as the webpage. The Firebug extension for Firefox is very helpful because it will list all the violations of the CSP. |
|||||
#16994 | Support for Clipboard API in Edge | assigned | Task | Must have (possibly next milestone) | ||
Description |
New Edge 15 implemented Clipboard API, so it will be nice to switch from our pastebin to real API in this browser. Note however that users report some errors (see comments in the linked thread). |
|||||
#10322 | support for creating accessible data tables | confirmed | New Feature | Normal | ||
Description |
We miss better support for creating accessible data tables i CKEditor. Would you consider distinguish between data and layout tables? (which are processed differently by assistive technologies such as screen readers). A Screen Reader Preview that helps authors further optimize content for accessibility would also be nice. Both functions are available in XStandard editor (We use this right now, but would like to shift to CKEditor) |
|||||
#4398 | Support for detaching from the DOM | confirmed | Bug | Normal | ||
Description |
Migrated from forum thread. TC
Result: Editor's content changes to "null" and it's not editable. |
|||||
#12089 | Support for inline-block editors | confirmed | New Feature | Normal | ||
Description |
Support for such editors could be useful: <div style="display:inline-block" contenteditable=true></div> <span style="display:inline-block" contenteditable=true></span> |
|||||
#2283 | Support for Java Facelets | confirmed | New Feature | Normal | ||
Description |
2.4-beta-1 does not have support for facelets. META-INF/faces-config.xml META-INF/FCKeditor.taglib.xml need to be added to support facelets. |
|||||
#12928 | Support for Lotus Notes | confirmed | New Feature | Normal | ||
Description |
We could make a research in the future if it is possible to support Lotus Notes in the same way as we support MS Word. We should check what HTML information is carried from Lotus Notes to browsers. |
|||||
#11120 | Support for multiple simultaneous Block level styles is missing | confirmed | New Feature | Normal | ||
Description |
After reading the documentation I thought it would be possible to apply many styles for an element. Yet in practice it looks like it's possible for inline styles, but not block level styles? This would a be very useful feature in a situation like this: config.stylesSet = [ {name: 'P1', element: 'p', attributes: { class: 'styled', elementclass: 'Emphasized'}}, {name: 'P2', element: 'p', attributes: { class: 'styled', elementclass: 'Draft'}}, {name: 'P3', element: 'p', attributes: { class: 'styled', elementclass: 'Quote'}}, {name: 'DIV1', element: 'div', attributes: { class: 'styled', elementclass: 'Draft'}} ]; I want to select multiple elementclass values with the shared class styled. The editor would reflect that the element is styled with one or more elementclass, but the actual style is context-dependent. For example users could mark a P element like this: "This paragraph is an Emphasized Quote" - the users custom stylesheet would then define the Quote and the Emphasis styles, which could both be active at the same time. Currently this is apparently impossible? If you think it's not useful or not possible, the documentation should clearly state that multiple block level styles is not supported. Also it's strange that the styling can change a P element to a DIV and back - a big semantic change. What if P and DIV allowedContent is different? I would prefer a config option to choose that the stylescombo dropdown only showed styles available for the currently focused element and the conversion could thus be avoided. |
|||||
#8378 | Support for optgroup | confirmed | New Feature | Normal | ||
Description |
For a better overview I want to have the optgroup element for select in one of my plugins. |
|||||
#7530 | Support for setting a default font and applying it through inline styles | review_failed | New Feature | Normal | ||
Description |
We would like to be able to set a default font for text in the editor. We realise this is currently possible using config.contentsCSS to specify a CSS file which defines the default stylings. However we require the default font styling to be stored within the document instead of in an external CSS file. <span style="font-family: arial;">sample text...</span> Would it be possible to implement a config option to specify a default font that will be applied like this to all text in the editor unless the user specifies a different font through the font drop down field? Alternatively could you provide an extension point that we could hook into to apply styling like this to text before it is inserted into the editor? Note: This request came from a customer and it is a feature that would be benificial in many of our products. |
|||||
#9660 | Support for Windows 8 Apps | confirmed | New Feature | Normal | ||
Description |
CKEditor 4 must be compatible to be used inside Windows 8 Apps. R&D is required on this to understand the current status and provide the necessary remedies for possible issues, as well as developer tools. |
|||||
#3731 | Support 'style only' override in style system | confirmed | New Feature | Normal | ||
Description |
This's a ticket derived from #705, which provide a UC of the following style definition which we don't support now: { element : 'strong', overrides : [ { element: 'b'}, { element: 'font', styles : { 'font-weight' : 'bold' } } ] } And a more generic UC ( and actually a common case )with 'style' only definition could be inferred as: { element : 'strong', overrides : [ { element: 'b'}, { element: '*', styles : { 'font-weight' : 'bold' } } ] } Which declare that we need to consider bold for the following two cases:
|
|||||
#7616 | Support window name in the popup plugin | confirmed | New Feature | Normal | ||
Description |
With the following changes the popup plugin was extended with window features, but it is still impossible to specify the popup windowName. It would be nice to add support for it, otherwise the file browser is opened in a new window each time (even if the corresponding window is already opened). The popup function in the CKEditor/trunk/_source/plugins/popup/plugin.js can be adjsuted to accept windowName: popup : function( url, width, height, options, windowName ) Thank you in advance! |
|||||
#8481 | switching between source and wysiwyg introduces gratuitous white space | confirmed | Bug | Normal | ||
Description |
Certain html snippets introduce extra white space on each switch between source and wysiwyg. In 6.0.472.63 (59945) Built on Debian 6.0.2, running on Debian 6.0.3, Iceweasel/3.5.16 (like Firefox/3.5.16), and recent versions of Safari the attached snippet exhibits the problem in at least 3.6.2 and the nightly build as of 2011-10-27. The behavior is somewhat different (less desireable?) with fullPage : true than without. In both cases each round trip wysiwyg->source->wysiwyg introduces a <p> </p> fragment. |
|||||
#11502 | Synchronous calls of asynchronous methods causes errors | confirmed | New Feature | Normal | ||
Description |
See e.g. #11295. Calling That's because developer has to care about calling methods when previous finished. There are callbacks and events which notify developer when action is completed, but it's his duty to find which method can be called when. However, not every developer understand problems with asynchronous methods and not in every case it's easy to handle this. For example when editor is loaded in one tab of some UI component and user switches between tabs too quickly, destroy() may be called before editor fully initialises. On the other hand, if editor's methods would take care of that (e.g. destroy() would wait until initialisation finished), then API would start to work unpredictably. Developer would never know if destroy() will be done immediately or if it's going to wait until something (setData, initialisation, etc.) ends. This may be even worse situation than the current one. We could make even longer step and make all editor's methods asynchronous and e.g. based on promises. Then everything would be fine... if you understand all of this :D. Therefore, instead of forcing developers to understand some not trivial concepts to do basic stuff we can simply clarify this in docs. But there still will be cases in which it will be hard to handle editor state (like the tabs case). Opinions needed. More details about the current situation in http://dev.ckeditor.com/ticket/11502#comment:8 |
|||||
#602 | Syntax highlight and go to line | confirmed | New Feature | Normal | ||
Description |
It would be a great idea to be able to use highlighting in source mode like you get in some text editors for coding. a button for go to line would be great because sometimes you have this huuuge files and you got an error on line 345. Would be great for debugging.
Moved from SF: |
|||||
#12463 | System hangs when using Image upload on IOS 8 (iPhone, iPad) | confirmed | Bug | Normal | ||
Description |
System hangs when using Image upload on IOS 8 (iPhone, iPad): Image Uoload Chose File "selected file" Send it to the Server SYSTEM HANGS !!!!!! This wad detected in version CKEditor 3.6.2 (revision 7275) used by my application, and HAS BEEN REPRODUCED ON YOUR DEMO KEditor 4.4.4 (Standard) (revision 1ba5105) |
|||||
#14632 | Tabbing through table merged cells creates invalid rows | confirmed | Bug | Normal | ||
Description |
Steps to reproduceTC1
TC2
Expected resultTC1&2: The new row has four cells. Actual resultTC1: The new row has one cell less at the end. TC2: The new row has only one cell. Other details (browser, OS, CKEditor version, installed plugins)Problem can be reproduced in all browsers from CKEditor 3.4 when creating row with TAB key was introduced. Please note that in CKEditor 4.x it works fine if I use "Insert Row Below" option. This can be used as a workaround. <table border="1" cellpadding="1" cellspacing="1" style="width:500px"> <tbody> <tr> <td>1.1</td> <td>1.2</td> <td>1.3</td> <td>1.4</td> </tr> <tr> <td>2.1</td> <td>2.2</td> <td>2.3</td> <td>2.4</td> </tr> <tr> <td>3.1</td> <td>3.2</td> <td>3.3</td> <td>3.4</td> </tr> </tbody> </table> |
|||||
#9002 | Tabelle cell lost after style has been applied | confirmed | Bug | Normal | ||
Description |
foo|bar|test foo|bar|<LEAVE THIS CELL EMPTY> foo|bar|test
--> The Empty cell is removed (TD is lost). It's now impossible to enter some text in this cell. |
|||||
#2510 | TAB jumps to next form field when in editor | confirmed | Bug | Normal | ||
Description |
Whenever I press the TAB key in the editor, the cursor jumps out, and onto the next form element (typically the submit button, in case of the FCK editor demos on fckeditor.net). If I press TAB in fullscreen edit mode, the cursor will seem to disappear, and whatever I type goes into the next field/button, while it's not visible. Mozilla/5.0 (X11; U; Linux i686; nb-NO; rv:1.9.0.1) Gecko/2008072820 Firefox/3.0.1 Ubuntu Hardy Reproduced here: http://www.fckeditor.net/nightly/fckeditor/_samples/html/sample01.html and here: http://www.fckeditor.net/demo |
|||||
#12285 | Tab key based navigation is broken in iframedialog plugin. | confirmed | Bug | Normal | ||
Description |
Problem is similar to #9611.
It isn't possible to jump (with tabIndex) through elements that are inside iframedialog plugin.
NOTES: |
|||||
#9611 | Tab key based navigation is broken inside specialchar dialog | confirmed | Bug | Normal | ||
Description |
It can be reproduced on v3 and v4. |
|||||
#829 | Table Auto Format | confirmed | New Feature | Normal | ||
Description |
Hi! Thanks for this nice application! But in version 1.6 Final, was a function at table properties named "Table Auto Format". In new 2.0FC i don't find it. Please, include it in final version, may be, as plugin? It's useful!
Moved from SF: |
|||||
#10655 | TAB leaves the editable when cannot indent anything | confirmed | Bug | Normal | ||
Description |
If we handle tab in all other lists' elements, then it should be blocked in the first one and in all other places where tab does nothing. It cannot be so inconsistent, because this is confusing and irritating. Either tab leaves editable or it indents lists/blocks. Not both at the same time. This could be configurable by keystrokes - by default tab is added as a keystroke executing 'indent' command. If someone needs it for leaving editable, then he can reset this keystroke. Or the opposite - tab by default can be used for navigation, but it's behaviour can be changed by setting a keystroke. And yes, there's no good solution ;|. |
|||||
#11017 | Table border value should only allow integers | confirmed | Bug | Normal | ||
Description |
Create a table. Specify table properties. Enter a border value. Floats are allowed, but XHTML indicates table border must be integer value. This causes our XHTML validation to fail.
|
|||||
#10375 | table cell horizontal split error | confirmed | Bug | Normal | ||
Description |
The far right of the back of the cell in the table to insert a new cell, horizontal split the cell error |
|||||
#14911 | Table cell lose formatting on tab switch an new text | pending | Bug | Normal | ||
Description |
Steps to reproduce
Expected resultThe new text has the same formatting (bold) like the text before. Actual resultIn Firefox and sometimes in IE the text lost the formatting. In Chrome not. Other details (browser, OS, CKEditor version, installed plugins)Browser: Firefox 45.3.0, Internet Explorer 11, Chrome 53 |
|||||
#17059 | Table cell properties - background color is not kept | new | Bug | Normal | ||
Description |
Steps to reproduce
Expected resultDialog with colors selection show current color of cell. Actual resultDialog with colors selection always show black color. Other details (browser, OS, CKEditor version, installed plugins)Checked on iOS and Chrome browser |
|||||
#12099 | Table Cell properties get duplicated on Chrome/Mac | confirmed | Bug | Normal | ||
Description |
While using Chrome in Mac OSX (10.8.5), any time you select a cell in a table and set a property(ies), the same property(ies) get cloned to the next cell in the same row. This does not happen using firefox. A way around it is to highlight the content of the cell instead of the cell itself before setting the properties. We tested this on the live demo to make sure it wasn't already fixed. |
|||||
#6272 | Table cells need ability to set additional styles | confirmed | New Feature | Normal | ||
Description |
Table cells need the ability to set the border-top, border-bottom, border-left and border-right properties so that you can set the border width, color and type as desired for each cell. In particular, it is currently not possible to set the border-top for one cell to none. It would also be helpful to be able to set a style and class tags for a cell like you do on the advanced tab of the table properties page. In general, it would be great to have an advanced tab for cell properties allowing you to set more things for each cell. |
|||||
#6258 | Table delete cells | confirmed | New Feature | Normal | ||
Description |
CKEditor has some problem with delete cells in tables. After delete any cell, table layout is incorrect. In my opinion we should remove option 'delete cells' (many editors working like that example Excel - only allow to remove row or column, no single cell) or after this action do colspan or rowspan to keep table layout stable. |
|||||
#16900 | Table from Excel gets pasted as image in Firefox | confirmed | Bug | Normal | ||
Description |
Steps to reproduce
Expected resultTable gets pasted as HTML Actual resultTable gets pasted as image Other details (browser, OS, CKEditor version, installed plugins)Probalem can be reproduced from CKEditor 4.6.2 in Firefox only. |
|||||
#14585 | Table insertion fires insertElement before moving cursor inside itself | new | Bug | Normal | ||
Description |
Steps to reproduce
Expected resultThe listener's action should be performed with the cursor inside the table, where it's presented to the user. Actual resultThe listener's action is performed at the location where the cursor was prior to table insertion. Other details (browser, OS, CKEditor version, installed plugins)I've verified this in the CKE nightly at http://nightly.ckeditor.com/16-04-13-06-07/standard/samples/ using FF 45.0.2 and Chrome 49.0.2623.112 (64-bit), both on MacOS X 10.11.4. |
|||||
#6584 | Table operation don't trigger DOM events / autogrow | confirmed | Bug | Normal | ||
Description |
To reproduce:
Result:
Same happens for probably all table operations: change style, class, etc. |
|||||
#14309 | Table or horizontal line disappeared after insert in case of numbered/bulleted list. | confirmed | Bug | Normal | ||
Description |
Steps to reproduceTested on demo page http://ckeditor.com/demo#standard
Expected resultInserted table/line should display and the next bullet/number in the list should appear. Actual resultThe inserted table or horizontal line disappeared. Other details (browser, OS, CKEditor version, installed plugins)I'm currently on CKEditor 4.5.3, but I can reproduce the problem on the latest CKEditor demo. The problem happens on FireFox 38.4, Chrome and IE11. |
|||||
#10021 | Table plugin uses attributes deprecated in HTML5 | confirmed | Bug | Nice to have (we want to work on it) | ||
Description |
When I insert new table, without any settings i get border="1" cellpadding="1" cellspacing="1" style="width: 500px;" attributes. These are unexpected and non-valid ones.
Edit: Easy workaround (aka solution): comment:13. |
|||||
#9743 | Table Properties For a Single Row Table not working properly | confirmed | Bug | Normal | ||
Description |
|
|||||
#10201 | Table properties have no width when opening dialog after resizing table | confirmed | Bug | Normal | ||
Description |
Result: Width has no value assigned.
This is happening because when using Firefox native resize handles, Firefox operates on attributes while CKEditor operates on styles what results in two widths (#9287). |
|||||
#16984 | Table Properties show invalid value for Headers when header is not the first row in the table | confirmed | Bug | Normal | ||
Description |
Steps to reproduce
Expected resultHeaders option shows "None". Actual resultHeaders option shows "First". Other details (browser, OS, CKEditor version, installed plugins)Problem can be reproduced in every browser starting from CKEditor 3.0. |
|||||
#11674 | Tableresize - allow percent-based values | confirmed | New Feature | Normal | ||
Description |
It would be nice if tableresize allowed to set column widths in percent instead of pixels. Of course, it should be configurable. |
|||||
#11939 | Table resize plugin should also allow resizing row height | confirmed | New Feature | Normal | ||
Description |
Table resize plugin should also allow resizing row height. |