This issue occurs when the ApplicationMenu is bound. The button in the ItemTemplate of the ApplicationMenu could be both RadSplitButton and RadDropDownButton. Their DropDownContent should not be displayed downwards, it should be displayed in the RightPane ( the Content of the Applicationmenu)

Declined: When the ApplicationMenu is in DataBound scenario the ItemsControl from which the ApplicationMenu inherits automatically creates ContentPresenters for each item and wraps their content. As the ApplicationMenu knows how to manage RadRibbonDropDown/Split buttons you will need to provide one of these containers as direct child of the  menu. You can achieve that using the following code, to show all items as RadRibbonDropDownButton:

public class CustomApplicationMenu : ApplicationMenu
    {
        protected override bool IsItemItsOwnContainerOverride(object item)
        {
            return false;
        }

        protected override DependencyObject GetContainerForItemOverride()
        {
            return new RadRibbonDropDownButton();
        }
    }

There are three errors for missing icons when implicit themes are used:
Resource '/Telerik.Windows.Controls.RibbonView;component/HelpIcon.png' was not found.
Resource '/Telerik.Windows.Controls.RibbonView;component/RibbonGalleryCollapsedIcon.png' was not f

We have a RadRibbonView with enabled KeyTips and a RadComboBox control below it.
We focus the RadComboBox and press "Alt + DownArrow". As a result the the RadComboBox is opened and immediately closed and KeyTip is activated and shown and the coressponding RadRibbonTab gets the focus. The expected result is that the RadComboBox is opened, remains opened and no KeyTips are activated.

RadGallery is used in RadRibbonView  and ListBox under the RibbonView with  DeferredScrollingEnabled set to true. When scrolling the Gallery, the ListBox Scrolls unexpectedly.

The KeyTips of RadMenuItems go behind the menu when hovering over the RadMenuItem. This issue seems to be related to the ScreenTip/ToolTip settings applied on the RadMenuItems - if no such settings are applied, the issue cannot be reproduced.
The Tooltip popup is placed over the KeyTips popup.

Allow the ApplicationMenu to be used as a stand-alone control



Available in R1 2017 Release

Implicit style doesn't apply on RadRibbonTabs which are added via PRISM.

UPDATE: An implicit style can not be applied on derived controls as their TargetType is different than the one defined in the implicit style. Basically if you set the style implicitly, the style is applied only on the types that match the TargetType exactly and not on elements derived from the TargetType value. You can find more information on the topic in the remarks section of the Style property definition: http://msdn.microsoft.com/en-us/library/system.windows.style%28VS.95%29.aspx

This is why in order to apply a Telerik predefined style on a UserControl deriving from RadRibbonTab, you  need to add a Style targeting the UserControl type in the Resources of the application. It is best to define that style after merging the Telerik ResourseDictionaries so that you can base the UserControl Style on the predefined "RadRibbonTabStyle".

Expose a property through which the TabContentPopup IsOpen state can be programatically controlled. This feature should allow the implementation of a scenario where the TabContentPopup is opened when hovering over the tab.

Declined: The current API of the RadRibbonView allow the users to control MinimizedPopup. A sample application is attached demonstrating how the Popup can me controlled

If you place a TextBlock in the QuickAccessToolbar and the Ofice_Black theme is applied you get black foreground on black background which makes the text unreadable. The content of the QAT must respect the theme applied to the RadRibbonView control.

Open the Application menu.
Open one of its submenus.
Hover another button.

The opened submenu will not close.

Available in LIB version: 2016.3.1017

Expose an event where the key combinations that (don't)show the KeyTips can be customized.

When the Ribbon is hosted in a RibbonWindow, the ContextualGroups are rended differently Q3 2013 release.

The ScreenTip isn't displayed unless you define its Title property

Expose property controlling the RibbonGroups Header Background

VS Designer trows exceptions if a RibbonTab is placed in a UserControl:  

If the RibbonTab control size isn't defined, the designer throws a System.InvalidOperationException - FrameworkElement_LayoutMeasure_InfinityNaNReturned.  

If the RibbonTab size is set, then clicking on the tab in the designer raises a System.ArgumentException - Property 'Items' was not found in the property collection 'Grid'. 

ElementName binding is not working in RadRibbonBackstage.

Reason for closing: The ElementName binding in Adorner is not supported and as the RadRibbonBackstage is Adorner it is not working there as well. Due to that framework limitation we cannot fix this issue and we will change the status of the feed back item to declined. You can find more information about the Adorner and its limitation in this article ( http://msdn.microsoft.com/en-us/library/ms743737%28v=vs.110%29.aspx ).

Posibility to use the QAT buttons when the BackStage is open

RibbonView: RadRibbonButton has inconsistent pressed/focused state

The styling in the controls vary when the mouse is down.
- RadRibbonButton gets a black border.
- RadRibbonSplitButton gets an dark orange border (when clicking the dropdown button)
- RadRibbonDropDownButton gets a grey line at the top

On mouse over
- RadRibbonButton and RadRibbonDropDownButton have a dark orange border with a white inner border
- RadRibbonSplitButton (dropdown button) does not get the white inner border

Reason for declination: 
Currently there is no way to unify the pressed state of these buttons because there is no Pressed state of RadSplitButton (the toggle and button parts has their own press visualization that comes from the default style of the corresponding buttons). 

If the height of the screen is smaller than needed the App_menu is clipped in the bottom. There are 5-10 px wrong in calculation

Expose properties to control the BackstageItem.Icon size