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.

Let's have a form in a host window and then replace (on a button click) the form with another form, using the LoadContent() method. The text of the tab is changed accordingly, but there is no update on the text of the caption.

If you try to close or set to autohide a ToolWindow in ActiveWindowChanged event and the ActiveWindowChanged is fired because you are trying to dock another ToolWindow (currently set to autohide), you may activate the wrong ToolWindow at the end.

When you try to close a hidden ToolWindow in ActiveWindowChanged, you are prevented from docking ToolWindows which are in AutoHide mode.

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.

RadSplitContainer designer is dependant on the RadDock assembly. This dependency should be removed. (ActionLists getter).

When a form that contains a RadDock is TopMost, AutoHide windows are shown behind the form

When the Form that contains RadDock is TopMost, the floating windows owned by the RadDock instance are not TopMost, so they go behind the form.

When RadDock.RightToLeft is Yes, the AutoHide tabs are positioned at the bottom of the AutoHideTabStrip, but not at the top.

When RadDock.RightToLeft is Yes, the close buttons are correctly aligned to left (but not to right as it is by default). However, the text is not aligned to right, so the close button overlaps the text.

When you change the text of a ToolWindow programmatically, this setting is not reflected on the titlebar of the TabStrip. The same issue appears for the title bar of RadForm when the ToolWindow is floating. Another case of this issue can be encountered for the AutoHideTab when the ToolWindow is in autohide mode.

When you have a big UserControl in a DocumentWindow and you scroll down this UC, the UC is prescrolled when you try to set the focus on a control of the UC.

If you have a FloatingWindow with Name and Text set to "TestForm", save the layout and load it, you get a Dockplaceholder with default Name and Text "ToolWindow1". 

If you first dock the FloatingWindow, then float it again and finally save and load the layout, you get information both about the docked and floating windows in the xml.

After a very specific sequence of steps, you may end up with an xml file of the RadDock layout that contains two windows, although there is only one window at the time the xml file is saved. In addition, when a floating window is loaded, it needs a click in order to get a caption string at the titlebar.

Let's have a ToolWindow in a RadDock. Float the ToolWindow and then close the FloatingWindow.
Save the layout, close the application and start it again. Load the layout and display the hidden ToolWindow by calling the DisplayWindow method. The ToolWindow will become docked instead of floating.

Images in TabStripItems of docked ToolWindows are upside down

When there is not enough space in the DockTabStrip for the tabitems which have images, these images overlap the neighbour tabitems.

When you have an AutoHideTab docked to right and you want to show an image and horizontal text,
the text is cut off taking the width of the image.

ActiveWindowChanged cannot be canceled if the event is fired for the case where you switch from one tab of a ToolWindow to another tab of a ToolWindow

An editor should appear at where the tabs of RadDock are when the end-user double-clicks the tabs or presses F2. This will allow him to change the text of the tabs.