Feature alignment with v2

[Garry Yao]

This list should be our last core feature alignments with v2:

#4358

List properties dialog box is missing

#4056

Hidden field problem

#4652

Config for disable editor context menu

#3582

Contents of anchors isn't visible

#5268

Port DragResizeTable to V3

#5404

FillEmptyBlocks in CKEditor 3.x

And some sample pages as well:

#5024

Port doctype samples from FCKeditor

[Alfonso Martínez de Lizarrondo]

Besides those tickets, we should port also the server side integration files that we want to support, I'm working on the asp version.

And take care also of the .Net and Java solutions (this can be done after 3.3)

The placeholder plugin is another sample that will be helpful for the people to customize their integration. In general, more samples means more code that can be used to test all the features and it can help to avoid basic questions.

[Frederico Caldeira Knabben]

Replying to alfonsoml:

Besides those tickets, we should port also the server side integration files that we want to support, I'm working on the asp version.

Be sure to follow ​the specs. You can base it on the PHP SSI, as always.

[Frederico Caldeira Knabben]

I'm removing entries we'll not be able to provide in the 3.3 from the list. Note that for these entries, we would prefer having the plugin repository ready first. This could be easily provided by contributors.

[Garry Yao]

As we certain blocking sub tickets, defer this to 3.3.x.

[Garry Yao]

Adding 'dragresizetable' plugin and 'fillEmptyBlock' configuration to list.

[Wiktor Walc]

I guess #5915 should go here as well (?).

[Charlie]

Would it be possible to consider adding back in the XML support for templates and styles? This would make behavior more consistant with V2 as there's no reason people should have to port over all those files is there? See #3588

[Frederico Caldeira Knabben]

@comp615, there is a very good reason for having js files instead of xml into the 3.x: cross-domain resources loading. In other words, a site in the "example.com" domain can load the editor (and the templates and styles files) from "otherdomain.org". This is not possible with XML.

For now, let's keep the discussion at #3588.