In the default control template of the RadSlider, the Track element is represented by a ContentControl control. When using the Xaml version of the assemblies, it would require extracting the TrackStyle, in order to base the custom one on it. An alternative would be to use the ChildrenOfType method to retrieve the ContentControl with x:Name="Track" and apply the needed modifications.

Both of these approaches could be a bit overwhelming when only the Width/Height properties of this Track element would need to be updated.

We could expose additional properties for changing the Width/Height values of this ContentControl (x:Name="Track").

Currently hiding certain ticks requires custom empty tick template or custom ticktemplate selector. When resizing such slider labels get overlapped because tick panel reserves space for the ticks - to preserve the proportions between tick values.

So user needs to use Canvas in the datatemplate of the tick.

The idea of this feature request is to somehow allow such feature out of the box with eventually additional property / behavior / built-in selector etc.

When you have set the value of the RadSlider to the maximum available and have placed the control within another element, lowering the width of the parent control does not cause the RadSlider to shrink as well.

This is reproducible when the deferred dragging is enabled and the slider is defined in a template (DataTemplate or ControlTemplate). The selection values are correct, but the UI of the selection is not properly updated. 

To work this around you can subscribe for the Loaded event of slider and reset its IsSelectionRangeEnabled property.

private void RadSlider_Loaded(object sender, RoutedEventArgs e)
{
	radSlider.IsSelectionRangeEnabled ^= true;            
	radSlider.IsSelectionRangeEnabled ^= true;            
}

Wokraround: Set the Selection property in the constructor of the window using the SelectionRange<T> struct.

public MainWindow()
{
    InitializeComponent();
    this.radSlider.Selection = new SelectionRange<double>(11,16);
}

The RadSlider supports the "increase" and "decrease" handles, but "decrease" only decrements SelectionStart, and "increase" only increments SelectionEnd. Ideally there'd be an option for *two* sets of buttons at each end of the slider, an "increase" and "decrease" pair, so that both SelectionStart and SelectionEnd could be *either* increased *or* decreased independently. See the attached illustration. Thanks! 

There is IncreaseDecreaseHandlesOnBothEnds SDK demo available since R3 2016 Release.
https://github.com/telerik/xaml-sdk/tree/master/Slider/IncreaseDecreaseHandlesOnBothEnds

Currently, the containers for the ticks are generated and added in the visual tree even when the TickPlacement is set to None. Think of an improvement so that in this case the ticks are not added in the visual tree.

When the Slider ControlTemplate is edited in Blend, the ticks of the control are not displayed.

Workaround:
The ItemsSource and ItemTemplateSelector of the RadTickBar controls "BottomTickBar" and "TopTickBar" is not set in the extraction process. To workaround this, set these two properties of TickBars and the ticks will be displayed ", for instance:
ItemsSource="{TemplateBinding ResultTicks}" and ItemTemplateSelector="{TemplateBinding TickTemplateSelector}".

Reason for closed:
This is an issue, that has been reported to Microsoft on several occasions (for example here: https://connect.microsoft.com/VisualStudio/feedback/details/677461/msdn-forum-the-value-of-itemscontrol-itemssource-is-missing-in-the-extracted-template )  and it is not scheduled to be fixed.

Expose an easier approach for styling the buttons that are placed over the slider's track. For example Style properties. Those RepeatButtons have their x:Names set to "LargeIncreaseHandler" and "LargeDecreaseHandler". 

Currently, in order to modify their appearance (like Background for example) you will need to override the entire ControlTemplate of RadSlider.

When the slider is hosted in a TabControl its bindings don't work as expected when switching tabs

Fixed in Q3 2014

When the slider is placed inside a ScrollViewer and the scrollviewer is resized fast a "Layout cycle exception is thrown".

The original scenario where we reproduce the exception is the following:
SelectionStart, SelectionEnd, Minimum and Maximum of the Slider are bound to DateTime.Ticks via converter.
Exception is not reproduced if you move the Mininum declaration in xaml before the Maximum. And same for SelectionStart = before SelectionEnd.

We are closing this item due to the workaround and the fact that it is NOT reproducible in WPF.

If your scenario is different, please open a new support thread with more information regarding this exception.

Add the ability to align the RadSlider ticks when they are used in custom TickTemplate. The ticks are currenlly always top/left aligned depending on the slider orientation.

Add possibility to input value like in the sliders from MS Expresion Blend 's ColorPicker

Implement Free/Lock/Push Thumbs interaction Modes like the ones in the Telerik RadSlider for Asp Ajax
http://demos.telerik.com/aspnet-ajax/slider/examples/thumbsinteractionmode/defaultcs.aspx

Implement out-of-the-box support for ToolTip to display the value during a drag even when the RadSlider.IsDeferredDraggingEnabled property is set to True.

Available in R1 2017 Release

Mechanism to allow/force a refresh/rebind of the data template for the ticks needed

Add PreviewSelectionStartChanged, PreviewValueChanged and PreviewSelectionEndChanged.