List properties dialog box is missing

[Wiktor Walc]

The properties for bulleted/numbered lists are missing (this feature is available in FCKeditor: when you click on a list, a "Bulleted List Properties" / "Numbered List Properties" item is available in the context menu).

The issue was reported here: ​http://cksource.com/forums/viewtopic.php?f=6&t=14342

[Denys]

You can view the missing bullet properties @ ​http://ckeditor.com/demo

When do you think this could be fixed? Is there a workaround? I need the speed of CKeditor but without the list properties I have to stay with FCKeditor?

[Denys]

Print-screen of FCKeditor function:

[Denys]

Possible workaround:

In the Style combo plugin (plugins\stylescombo\default.js), add an attribute for the ol element (or the ul element). For example, for roman lists:

CKEDITOR.addStylesSet('default',[
{name :'Roman',element:'ol',attributes:{type:'I'}},
]);

It works BUT to apply the style, the ol element must be selected. The only method I saw is to select it via the name of the element shown at the bottom of the editor. Not very user friendly for casual users. (see the CKEDITOR FAQ ​http://cksource.com/forums/viewtopic.php?f=11&t=17301)

[Garry Yao]

Thanks kurgbe, we should be able to align this feature with v2 in this milestone, the styles combo is not sufficient to carry out this feature, we still need a classical dialog here.

[Garry Yao]

Alternate bulleted list type in IE doesn't work (it should be circle instead of "Circle"), besides, in V3 we should deprecate the "type" attribute in favor of ​list-style-type CSS property.
Also please use "<not set>" for unknown list type instead of leaving it empty.
Besides, Can we make the Bulleted List Type field a bit wider, make it looks better?

[Garry Yao]

Please use "<not set>" instead of 'inherit' as display option, which is more user-friendly, it's enough to just delete the style when "<not set>" is selected. Also this option is missing from the Bulleted List type.

[Garry Yao]

Also note that while adapting to the CSS style, we should still provide compatibility to the "type" attribute which make comes from content produced by v2.

[Denys]

Thanks for the patch. Suggestion: instead of <not set> or <Inherit> we could use <Default>

[Minh Nguyen]

I using '<not set>' for user doesn't select type of list.

[Garry Yao]

Finally, we need a mapping between attribute ​type and ​list-style-type.
Also, it's enough to use empty string for 'notset'.

[Garry Yao]

That's great, but I think you misunderstood my points that the mapping should be applied to the 'setup' of list type instead of on 'commit':

this.setValue( element.getStyle( 'list-style-type' ) 
        || mapListStyle[ element.getAttribute( 'type' ) ] 
        || element.getAttribute( 'type' ) 
        || '' );

[Minh Nguyen]

Thank Garry, I have got your point.

[Garry Yao]

There's a problem with the current approach(also v2), with the following list, it's not able to recognize the list type properly.

<ul type="i">
	<li>item</li>
</ul>

Also, I can't get the 'start' field working.

[Garry Yao]

Be sure the following thing will happenen before committing:

1. Register plugin into core config in alphabetic order;
2. Run lang tool to update all other language files;

[Minh Nguyen]

Fixed with [5409].