When you open the Advanced Layout Designer of RadDock and you try to reposition a ToolWindow by a drag-and-drop operation, the designer closes unexpectedly. This issue happens when there is a specific layout created.

In addition, if this ContextMenu is called from a control contained in an autohide DockWindow that is currently expanded, this window becomes collapsed.

RadDock does not show tooltips on certain buttons. The issue actually comes from OverflowDropDownButtonElement which has issues with its ToolTipText property.

Visual Studio 2010 document window behavior

If you have several textboxes anchored to Left, Top, Right in a Form hosted in RadDock and you redock the window so that its width remains the same, the width of the textboxes will change.

If you change the name of a child mdi form in its Load event, this title will not be reflected by the tab of the document window created to host the child form.

Comes from ticket 371813;

1)Create a form with RadRibbonBar, RadDock with some (3) windows, set key tips to the RibbonBar and run the form.
2) Hold and release the Alt key. The numbers show up on the ribbonbar as expected.
3) Click somewhere but not on the tabdocument to turn off the numbers ( notice that the initial tab will be "documentWindow1")
4) click on "documentWindow3" to select it
5) press the the Alt key again. The tabs will switch back to "documentWindow1" !!!

When you set the Cancel property of the DockWindowCancelEventArgs in the ActiveWindowChanging event, the active window should not be changed.

This feature request refers to introducing a new ToolWindow property which will allow setting individually text to the ToolWindow's Caption and Tab.

The AutoHide and Docking button of the toolWindows does not have a localization strings. Same with the document window.

If you have a ToolWindow in AutoHide mode with a RadDropDownList in it and you choose an item from the list or scroll the items in the list, the ToolWindow will hide itself.

When a floating window is hidden and RadDock layout is saved, the hidden window is saved in its Docked state and displayed as Docked when layout is loaded.

If there is a RadDock in UserControl and second UserControl, which inherits the first one, then the RadDock€™s layout in the second UC is damaged in design and run-time.

RadDock should support a MDI mode where the child mdi forms are displayed in the old fashioned way.

RadDock should have ActiveMDIChild property which returns the currently activated mdi child.

Resolution: 
Use the ActiveMDIChild property of the parent form. 

Let's have a TextBox, ToolTip and a FloatingWindow containing the TextBox. The following code snippet will not show a tooltip for the textbox:
            this.toolTip1.ToolTipTitle = "ToolTip";  
            string strToolTip = "Exemple";  
            this.toolTip1.SetToolTip(textBox1, strToolTip);  
            this.toolTip1.AutoPopDelay = 32767; 
            this.toolTip1.Active = true;

Place a RadTextBox on a Form and sets its Anchor to Left, Top, Right. Let's say this form is a MDI child and RadDock hosts it. You will notice that the RadTextBox appears with a wrong size and a part of it is actually invisible.

If you try to set this this.toolWindow4.TabStrip.SizeInfo.SizeMode = SplitPanelSizeMode.Absolute , the TabStrip will not stay fixed if the form containing RadDock is resized. However, if you hide the main document container, this setting will start working.

Let's have a RadDock control hosting several MDI child forms. Set the MDIParent property of these forms to null. The forms will become top level windows, but the HostWindows will not be removed and RadDock will continue listening to the events of the forms. MDIChildren will still contains the forms as well.

When you set a ToolWindow in AutoHide DockState, hover the tab of the AutoHide window and set the focus to the window by a mouse click operation, you are not able to hide the window right after you click outside of the window.