It would be nice to have a calculator input field.

Navigate to:

http://localdemos.telerik.com/aspnet-ajax/treelist/examples/databinding/loadondemand/defaultcs.aspx

1) Expand item with ID:2, then items: id:1413, id:1414

2)Expand item id:1

3)Fill Item ID textbox with "303" and Level textbox with "2"

4)Click "ExpandItemToLevel"

5)The icon of item 304 seems like "expanded"(and it should be), however the item is not expanded.

With the current implementation if the RenderMode is set to Auto in the web.config file it is later automatically changed to Leightweight instead of Mobile.

Creating a large page with RadEditor control and opening the mentioned dialog will scroll the page to the top. This causes the user to loose visual  contact with the Editor.

The issue is due to the automatic textarea focusing in the clientInit() method of the dialog's logic.

To resolve the issue you should modify the dialog and remove the focusing functionality. To do so follow the next steps:

    1. Follow the Custom Built-in dialogs approach (http://demos.telerik.com/aspnet-ajax/editor/examples/externaldialogspath/defaultcs.aspx) to use an external and later modified Plain Paste Dialog - the MozillaPasteTextDialog.ascx;
    2. Find the clientInit() method trough the client-side logic of the MozillaPasteTextDialog.ascx file;
    3. Remove the this._container.focus() line.

You can also find attached a sample page with the fix placed, so that you can examine it.
 

When trying to align selected text in a table, not all cells are being aligned correctly under IE and Chrome. In Firefox only one table cell is being applied with the chosen modification and not the selected text.  

Under IE and Chrome, when a table row element is in the selection, the child td elements are not processed by the Align command.

Under FF when the table text is selected, the selected element is only the first TD element. 

The problem under IE and Chrome could be resolved using the following override of the executeOnNode():

<telerik:RadEditor runat="server" ID="RadEditor1">
</telerik:RadEditor>

<script type="text/javascript">
	Telerik.Web.UI.Editor.AlignCommand.prototype.executeOnNode = function (node) {
		var utils = Telerik.Web.UI.Editor.Utils;

		if (utils.isTag(node, "table"))
			return;//prevent alignment of tables since this has no effect in browsers.

		if (utils.isTag(node, "tr")) {
			var nodes = node.childNodes;
			var nodeArr = [];

			for (var i = 0; i < nodes.length; i++) {
				nodeArr.push(nodes[i]);
			}

			while (nodeArr.length) {
				var childNode = nodeArr.shift();
				if (this.isSuitableNode(childNode))
					this.executeOnNode(childNode);
				else
					this.executeInlineNode(childNode);
			}

			return;
		}

		if (utils.isTag(node, "ul") || utils.isTag(node, "ol"))
			return this.executeDomCommand($.makeArray(node.children));

		if (utils.isTag(node, "img")) {
			if (this.nodes.length == 0 && this.canAlignImage()) {
				if (this.options.align == "none")
					this.alignBlock(this.getBlockContainer(node));

				return this.alignImage(node);
			}
			else {
				this.removeImageAlign(node);

				var imageContainer = this.getBlockContainer(node);
				if (imageContainer != node)
					this.executeOnNode(imageContainer);
				else
					return this.executeInlineNode(node);
			}
		}

		this.alignBlock(node);
	};
</script>

In an effort to better promote Client-Side development that leverages your API, I recommend you update your demos that capture and log events (such as http://demos.telerik.com/aspnet-ajax/input/examples/programming/clientside/apievents/defaultcs.aspx) to behave and act more like the Web Developer Console logging of objects (treenode). 

You could put a control together on the page, but I was thinking at the very least you could just add the console.log lines on these demos.. 

Also, I did a page recommendation on one of your documentation pages that covered clients side events on RadTextBox (I believe).. An event capturing demo that doesn't link to Telerik's EventArgs is kind of pointless to me.. but it would seem there isn't much documentaion in this area. So console logging the event args is just about the best way to review them.