Custom Query
Results (101 - 148 of 148)
Ticket | Summary | Keywords | Owner | Type | Status | Priority |
---|---|---|---|---|---|---|
#5998 | Sample config.js file (config.sample.js perhaps) | Discussion | Task | new | Normal | |
Description |
It is sometimes very confortible to have a prepared config file where You could see all the available configuration (commented out) and its documentation without having to go online and search what configuration parts are worth to be added to some particular project (it takes less time to go through config text file). I have made such sample configuration file and would like to suggest to add it to the project. It is based on the official documentation and at the moment - up to date. In the first usage examples I have placed default values instead of writting them seperately. |
|||||
#6173 | Removing Items from unordered list (WinXP/IE8) | IE Discussion | Bug | confirmed | Normal | |
Description |
I've got a problem with unordered / numbered lists with IE8 on WindowsXP.
This error is not in Firefox3 (WinXP), but IE8 (Windows7) This is also the case in http://ckeditor.com/demo/ |
|||||
#6184 | Better HTML code clean up | Discussion | New Feature | closed | Normal | |
Description |
We are mainly focused on cleaning up the content while pasting, but there is still a lot of content in various systems that was created long time ago that may contain broken / invalid HTML. Suppose we have the following HTML source at the beginning: <p><font face=""><font face=""><font face="">fooo</font></font></font></p>
The |
|||||
#6258 | Table delete cells | Discussion | New Feature | confirmed | 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. |
|||||
#6294 | insertHtml: support for custom (invalid) HTML tags | Discussion | Bug | confirmed | Normal | |
Description |
There might be a situation, when one wants to use a custom tag, for example to process it on the server side later. There is a problem with handling custom tags when inserting the content into the editor. When checking the _samples/api.html sample and trying to paste the following content into the blank wysiwyg area with the "Insert HTML" button:
the result is as follows (tested in rev 5872):
When switching from the source mode to wysiwyg mode and back with the following HTML:
the result is correct in all cases:
|
|||||
#6359 | IE selectable area in blank wysiwyg editor is very small | IE Discussion | Bug | closed | Normal | |
Description |
[Expected] clicking anywhere within the white editing area will focus the editor. [Actual] The clickfield to accomplish the expected result is very small - only the area shown in the attached image. Clicking anywhere outside of that area will focus the editor's containing element and will not permit editing. The available clickfield is dependant on the amount of content within the editor, however it's always possible to click on a 'dead zone' and lose focus. (E.g., go to ckeditor.com/demo and click to the left of the word "tells" below the picture of Little Red Riding Hood.) Other details which may or may not be useful: We had implemented a workaround for this which relies on IE7's moveToPoint and was able to fix the vast majority of IE's quirks that cause this problem. Unfortunately, IE9's implementation of moveToPoint differs, and so our workaround is gone. A slight improvement is to detect the failure case and simply focus the editor (which at least makes creating a new article in IE9 feasible), however there are a lot of edge cases which that fails to cover (dragging a selection in and out of the dead zone, etc.) |
|||||
#6443 | SelectionChange not firing in all instances | IBM Discussion | Bug | confirmed | Normal | |
Description |
Run the attached code example. Click to put the cursor at beginning of first line - event fired. Now drag select within the same line - event NOT fired. Now drag select within the second line - event fired. |
|||||
#6565 | The Anchor dialog window should let the user set the ID for an anchor | Discussion | Bug | closed | Normal | |
Description |
The Link dialog window lets the user choose an anchor from a drop-down list by its ID. However, the ID for an anchor can only be added while editing the source and not via the UI. Providing an option to add an ID to the Anchor dialog window would make the system more consistent. |
|||||
#6592 | BIDI: Show block tag name mirroring | Discussion | New Feature | closed | Normal | |
Description |
'showblocks' outlook should have the similar mirroring effects with indentation commands. |
|||||
#6602 | Automatically send WYSIWYG browsers into source mode instead of refusing to work | HasPatch Discussion | New Feature | new | Normal | |
Description |
Browsers that don't support tag editing still support ckeditor's source mode, which is better than nothing, and provides a more gradual operational decline. My suggested patch creates a env.isTextCompatible var, and if env.isCompatible is false but env.isTextCompatible is true, ckeditor defaults to a text entry mode with limited, but still existent functionality. |
|||||
#6604 | Bidi and Justify plugins should create the same element [enterMode BR] | Discussion | Bug | closed | Normal | |
Description |
Currently, when enterMode is BR, justifying text results in a paragrpah, and adding direction results in a DIV. In both cases paragraph should be used. |
|||||
#6612 | Table right alignment floated | Discussion | Bug | closed | Normal | |
Description |
The 'align' attribute used on table element actually makes the table right floated.
|
|||||
#6623 | Colors dialog: up/down arrow keys not working as expected | Discussion | Bug | closed | Normal | |
Description |
In the first colors dialog that appears straight after pressing "Text Color" or "Background Color" button, the up/down keyboard arrow keys doesn't work as expected - pressing the down key moves to the next color on the right side instead to the next color in the line below. It looks like it never worked properly. |
|||||
#6635 | Enable MS-Word styles by default | Discussion IBM | Task | closed | Normal | |
Description |
From time to time we receive incompleteness structure when pasting from MS-Word (#6484,#6608) because by default "pasteFromWordRemoveFontStyles" is disabled, which strips inline styles delivered by the application. While the original intention was to keep the output clean, it nows seems more reasonable to accept those styles than loose them. |
|||||
#6643 | Ctrl+V on Windows XP with FF pastes local image | Discussion | Bug | closed | Normal | |
Description |
Hi, I'm mike from the OTRS project. We use CKEditor in our open source software, and generally our users are really happy with it. One thing that we found out recently is that if you're on Windows, with Firefox 3,6, you can paste an image in the editor by clicking Ctrl+v on the keyboard. If you do this on Win7 or WinVista, then the result is a broken image icon diplayed in the editor. If you look at the source there's an <img> tag which points at the file in the users temp dir on the local hard drive. However, if you use Firefox 3.x on WinXP apparently the image IS displayed properly inside the editor so it LOOKS like the image is there, only obviously the path is still local. This is nastier because the user THINKS it worked, and submits the entry. Only for anyone using a different PC the file is not in this location, so they don't see the image. Inserting an image using the image button in the CKEditor toolbar works just fine. 1.) CKeditor should stop making Ctrl+v with image data on the clipboard insert broken <img> tags? 2.) since apparently the link to a file is available, it would be great if this same action could open the image dialog with the link to the local file pre-populated. We even have users who reported that it works for them already in the way described in 2) just I could not find the browser/OS combination to reproduce that. |
|||||
#6668 | Image resize plugin | Discussion Webkit Drupal | New Feature | closed | Normal | |
Description |
I guess it's known but I couldn't find a related report: there's no image resize in Opera, Safari, Chrome. I guess browser support and/or a plugin is needed? |
|||||
#6697 | Non-editable content duplicated on drag-n-drop | Discussion | Bug | closed | Normal | |
Description |
Test:
IMO, when drag-and-dropping non-editable blocks, the following should happen:
|
|||||
#6702 | insertElement on top of text selection | Umbrella Discussion | Bug | closed | Normal | |
Description |
Unlike "insertHtml", "insertElement" invoking that happens on a text selection in structure like table and list either leaves a malformed DOM or even an error. The following tickets are associated:
|
|||||
#6707 | Paste over selected texts changes styling of pasted text | Discussion | New Feature | closed | Normal | |
Description |
It seems as the when selecting text in the editor and pasting over that, the paste keeps the previous styling in some strange way. To reproduce: Select the text below and paste into a empty editor:
Start text: After the text has been pasted. Do ctrl+a to select all and then ctrl+v to paste the same text again. All text is now bold. Repeating this introduces a new nested bold tag each time.
I understand that this is a area where different people would argue that different behavior is right. My opinion is that MS word behavior makes sense to me. |
|||||
#6776 | Proposal: remove obsolete translations | Discussion | Task | closed | Normal | |
Description |
Currently there are many translations that haven't been updated for a very long time. They take extra space for the people that don't mess too much with the provided files and with so many missing strings they are hardly useful for the end user. There are also some files like the Canadian French that it's quite less updated than the regular French file, so I wonder if the users prefer to look at some words better translated to their country locale or see more words in French instead of English. (besides the fact that many times both translations could be used for all the French countries as the difference could be really just a point of view of the translator at that moment but it's possible to have a single file). I will remove any obsolete translation in the next release of Write Area with CKEditor, removing the files with over 200 missing entries saved 90Kb, so I think that I might go ahead and even remove the ones that are over 100 missing entries. Of course, a call to the translators should be done in order to try to find people that can take some time to update its locale if he doesn't want it removed. |
|||||
#6824 | Alignment is not observed after paragraph format has been applied | IBM Discussion | Bug | closed | Normal | |
Description |
Steps to reproduce the defect:
Expected: The cursor stays Right Aligned (or Centre Aligned). Actual: The cursor becomes Left Aligned. |
|||||
#6835 | A few dialogs' content is not resiable | Discussion | Bug | review_failed | Normal | |
Description |
In a few dialog we have fixed width for content, so the dialog is resizable but the content size is never changed.
|
|||||
#6892 | BIDI: Incorrect behaviour when copying and pasting RTL list from within a table | IBM Discussion | Bug | closed | Normal | |
Description |
Steps to Reproduce:
Expected: The Bulleted List that was pasted outside of the table has RTL language direction. Actual: The Bulleted List that was pasted outside of the table has LTR language direction. |
|||||
#6931 | Form creation behaviour | Discussion | Bug | new | Normal | |
Description |
IMO forms creation should be much like DIV creation, wrapping the selection rather than removing it. |
|||||
#6934 | Alternative style/format outlook | Discussion HasPatch | New Feature | new | Normal | |
Description |
Style combo item is not presented under the preview style of the each style definition (same with format combo), sometimes this isn't an option at all (seen on user request #6379), the editor should allow an alternative presentation to be provided in the following format: { name : 'Colored: White', element : 'span', styles : { 'color' : 'White' }, displayHtml: '<span style="background-color:#000;color:#fff;">Colored:White</span>' } |
|||||
#6937 | Applying Block Quote to empty or the only paragraph in Table cell applying Block Quote to Table instead of Table Cell or Paragraph in Table Cell | IBM Discussion | Bug | new | Normal | |
Description |
To reproduce the defect: Scenario 1:
Expected Result: Block Quote is applied to Table Cell. Actual Result: Block Quote is applied to whole Table. Scenario 2:
Expected Result: Block Quote is applied to the selected paragraph inside Table Cell. Actual Result: Block Quote is applied to whole Table. |
|||||
#6948 | Styles combo should more accurately reflect the selection | Discussion | Bug | pending | 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". |
|||||
#7017 | [IE] Table cells deleted when trying to set formatting for the entire table | IE Discussion IBM | Bug | confirmed | Normal | |
Description |
DUP with a better description: #7220. Test/Use Case
In MS Word, user is allowed to select whole table by clicking [+] in left upper corner, then it is possible to set unified format to all table cells and resizing. CKEditor also allows selection of whole table for resizing.
Instead of resize try to change formating
Result in IE6 - part of cells are deleted <h3 style="color: blue"> </h3> <h3 style="color: blue"> </h3> <h3 style="color: blue"> </h3> <h3 style="color: blue"> </h3> <table border="1" cellpadding="1" cellspacing="1" style="width: 500px"> <tbody> <tr> <td> </td> </tr> <tr> </tr> <tr> <td> </td> </tr> </tbody> </table> <p> </p> In CKEditor v3.5 it was not possible to select style when table resize icons were visible Should it be possible to set formating this way? Or when resizing table, setting format should be disabled? In Opera, formating is set outside of selected table, but without changes inside. <h2> </h2> <table border="1" cellpadding="1" cellspacing="1" style="width: 500px"> <tbody> ... In Firefox, only first cell got formating |
|||||
#7120 | Line Spacing Button | Discussion | New Feature | new | Normal | |
Description |
as in MsWord, it looks nice to have line spacing option as in button click: -Space Sizes List -add/remove spacing after paragraph -add/remove space before paragraph I Think this will completethe editor to be as perfect as using MSWORD. |
|||||
#7356 | Style::removeObjectStyle something might be wrong | Discussion | Bug | closed | Normal | |
Description |
At the very least, in that function the var styles = CKEDITOR.style.getStyleText( def ); isn't used, but the final part to remove the style has remained that way since it was created in [5847] that changed also the applyObjectStyle but was reverted in [5978] So a little clean up is needed there, deciding if it must use getStyleText or def.Styles (but using a local variable), and correcting the comments. |
|||||
#7796 | Paste as Plain Text Behavior - FF vs. IE | IBM Discussion | Bug | closed | Normal | |
Description |
Run attached example. Copy "Sans" from first line. Paste as plain text at end of second line. On IE, the copied font is maintained. On FF, the text is pasted with default font. Is this a browser difference? |
|||||
#7966 | Error suggestion not correct when we enter invalid values for width & height fields in Table dialog | IBM Discussion | Bug | closed | Normal | |
Description |
To reproduce the defect: In the Table Properties enter invalid values(-20 or 35ex) for width and press OK button. Expected Result: An error dialog comes up with a waring message width must be a positive number greater than zero and valid CSS units are px em % . Actual Result: An error dialog comes up with a waring message Specified value must be a valid CSS length unit same issue when we enter invalid value for Height This is not satisfying the criteria for A11y Checkpoint 3.3 |
|||||
#8260 | Change from raising error to show an alert if instance exists | Discussion | Bug | new | Normal | |
Description |
Split from #8226 I think that many new users don't realize that they have errors in the console (after all IE is the only browser that currently shows clearly when a page has a js error). We must remember that many people aren't javascript developers, that's why they use things like the asp.net or Java adapters, they just know how to work at the server side and when they try to copy some javascript code as shown in some examples and doesn't work they don't understand what's the problem.
So I strongly suggest to change
|
|||||
#8716 | Better indication of required fields | IBM Discussion | Bug | confirmed | Normal | |
Description |
Labels for all required fields on our dialogs should have an astrisk(*) and instructions for identifying required fields should be clearly labeled at the beginning of the form. This is a failure of Accessibility Checkpoint 1.3.1 This is clearly documented in Examples of Success Criterion for 1.3.1 See links here.. http://www.w3.org/TR/2012/NOTE-UNDERSTANDING-WCAG20-20120103/content-structure-separation-programmatic.html |
|||||
#9255 | Styles.js - should it stay in the root folder? | Discussion | Task | closed | Normal | |
Description |
What's exactly the problem with this file?
It contains sample data used exclusively by two optional plugins (if I'm correct): stylescombo and div. In fact the default
If Proposed solution:
Point (3) leads to some additional problems:
Last word regarding core...
Comments in |
|||||
#9526 | [IE] Selection is not properly reflected on startup | IE Discussion | Bug | new | Normal | |
Description |
|
|||||
#9614 | Tabletools insert column before behavior is confusing | Discussion | Bug | new | Normal | |
Description |
I'm a little bit concerned about the expected behavior of "insert column before" for the following case: +-----+------+ | 1.1 | 1.2^ | +-----+------+ | 2.1 | +-----+ How it works now: +-----+--------+------+ | 1.1 | | 1.2^ | +-----+--------+------+ | 2.1 | +-----+ How it should look like in my opition: +-----+--------+------+ | 1.1 | | 1.2^ | +-----+--------+------+ | 2.1 | | +-----+--------+ Most likely this is not an issue but it brings some confusion. The origin of this issue is in #9609. |
|||||
#9656 | Should event.on/removeListener handle one listener attached multiple times to one object,event? | Discussion | Bug | closed | Normal | |
Description |
Question based on http://dev.ckeditor.com/ticket/9622#comment:4 Solution (or lack of it) should be discussed first. |
|||||
#9849 | Orphan <br> should be transformed into <p><br></p> | Discussion | Bug | new | Normal | |
Description |
We do several inline elements fixing that are found orphan inside body. This was true for <br> as well, until we reverted a fix that was causing #9167. Because of that, I've commented out a test made for that case form dt/core/htmlparser/fragment.html, test name "test_parser_13". It is still unclear for me the cases for this fix, but considering that we were used to do so, we should keep doing it. I'm just unsure if this is necessary. |
|||||
#9850 | Dialog that doesn't fit in viewport can't be moved by dragging | Discussion | Bug | confirmed | Normal | |
Description |
Extracted from #8888. |
|||||
#9855 | Better context checking for toolbar buttons | Discussion Drupal | New Feature | new | Normal | |
Description |
There is room the enhance the context checking we do for several toolbar buttons. While the current approach is correct, it can be optimized to better fit user's intentions, helping on the UI usability. One good example for that is related to object selections. There is no much sense on having inline styles, like bold, enabled when an image is selected. Let's open a discussion and analise all possible cases first. |
|||||
#12859 | Errors when trying to call some editor methods too quickly (synchronously) | Discussion | Bug | closed | Normal | |
Description |
Why CKEditor fails when I try to call some methods one after another? editor.setData( someData ); // somewhere later... editor.destroy(); The answer, unfortunately, isn't simple. Otherwise we'd have this fixed a long time ago. This is a mix of history, backwards compatibility, architectural limitations and lack of good solutions.
First thing to notice is that this is not only
Second thing to notice is that this problem occurs not only when editor isn't loaded yet, but also when switching between states and setting data (both operations can be asynchronous). This introduces more variables to the equation and could even make the state checks pretty ugly. Fortunately, we introduced
Another architectural aspect that would have to be taken into consideration is how the code is decoupled. For instance, the Backwards compatibility is important for one more reason - we can make backward incompatible changes, but we must do them in a smart way. For instance, once it's done it should be final - we can't ship some other solution in the next major release if this one turns out to be unsatisfactory. This rises the stake pretty high. The last thing, and actually the most unfortunate, is that throwing errors is not that good solution. It may tell you that you're doing something wrong, but it won't tell you when you can do it. try { editor.setData( ... ); } catch ( err ) { if ( err instanceof CKEDITOR.editorNotReadyError ) { // apparently, it wasn't the right moment // ... and what now? Ok, let's wait for some imaginary "ready" event // (which doesn't exist right now): editor.once( 'ready', function() { editor.setData( ... ); // ... actually, this could throw again if some other editor#ready // listener called setData too and haven't cancel the event. } ); } else { throw err; } }
Isn't it ugly? I think it's a terrible developer experience. A more useful approach would to be cache method calls and execute them when the editor reaches the correct state. But this would mean that for instance To sum up. I don't want say that fixing this in CKEditor 4.x is impossible, but for now we didn't have enough resources and well... courage, to attempt that. I would also risk a statement that it's late in CKEditor 4.x for such changes. But most importantly, we are aware of these problems and will definitely design CKEditor 5's API differently. |
|||||
#13205 | Advanced Toolbar Configurator on wide screens | Discussion | Task | new | Normal | |
Description |
I think we could style differently Advanced Toolbar Configurator on wider screens. Imho it looks a bit weird now on such screens. |
|||||
#1936 | Inline spelling support? | Discussion | New Feature | closed | Low | |
Description |
Some of the big webmail providers (e.g. Google, Yahoo) have Ajax spell checking with in-line marks showing typos, and a drop down menu of suggestings. Any possibilities to integrate such for FCKeditor would be a home run! |
|||||
#2578 | Opera browser fit to width loses edit area | Opera Discussion | Bug | confirmed | Low | |
Description |
When using the Opera browser (V9.52 on Windows XP), if I change the view settings to 'Fit to Width' then the edit area of the FCKEditor disappears. The buttons remain however. This happens within my instance of the editor and also on your demonstration page using V2.6.3 of your editor. |
|||||
#3385 | toString() for easy debugging | Discussion | New Feature | closed | Low | |
Description |
Perhaps it's better to implement the 'toString' method on some core objects to help the debugger(e.g. Firebug) having a text presentation for them, which is friendly for debugging. |
|||||
#3724 | Slow and unusable editor when inserting 999x99 table | Discussion | Bug | closed | Low | |
Description |
When we insert a table with 999x99 cells, Firefox get slow and editing is no more possible. This test is not something users often do, but one of my clients did this test... Perhaps a limit should be fixed ? |
|||||
#9988 | Stop using <a> for everything. | Discussion | Task | confirmed | 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. |