Provide a way to set .5 and display it like 0.5 , not 5.0 in No-Mask Numeric input.

When you set the IsCurrencySymbolVisible to false and Mask="1.x" you are not able to fill the first digit. 
For example if you want to insert 1.234 and you press 1 the control fills 0.001 and all other digits can be added at the last position only.

Supporting DateTimeOffset for DateTime masks

Having a Value of type 550.123, then selecting "55" and changing it to 7 produces 7.123 instead of 70.123.

Possible workaround is using no-mask (Mask="") and FormatString.

Currrently the default ContextMenu of the TextBox inside the MaskedInput is used. You have to set it to null in code behind and the create custom ContextMenu in XAML / Code behind to use it successsfully.

Currently the MaskedInput controls cannot handle properly Chinese input symbols from Google Pinyin or MS IME.

MaskedInput's code relies on methods from TextBox which do not fire when the input is not from keyboard.

We have MaskedTextInput with InputBehavior set to Replace.

When we select part of the value or the whole value and then insert a symbol, only the first selected symbol is replaced but not the whole selected text.

If you enter the placeholder character in a MaskedInput, it will be processed as an empty position. And if the InsertBehavior is Input, the positions containing the placeholder chars will be overriden if the user keeps entering characters after the end of the allowed input is reached.

Use the new implict mechanism. Attach the Windows8 _Wpf project instead of Windows8 dll. Xaml parse exception occurs runtime - 
"Cannot set unknown member 'Telerik.Windows.Controls.MaskedInput.PreviewInputTextBox.IsReadOnly'."

Note: you can try the workaround added here: http://stackoverflow.com/questions/6850713/weird-xaml-parsing-error-when-trying-to-set-textbox-isreadonly

In PreviewKeyDown we change the Foreground of the MaskedInput when the Key is Return. Then we revert the color on other key press. Changing the focus returns the color set on Return but it shouldn't.

Support entering a single digit in a DateTimeMaskedInput control with Mask="MM"

SelectAll then Shift + Del makes the need of twice (Ctrl + Z) for successful undo operation.

In MaskedTextInput, users need to enter from right to left just like in NumericInput and CurrencyInput.

Allow entering an input in (exponent) scientific notation form for the RadMaskedNumericInput control

When two or more MaskInput controls are focused at the same time, the application freezes.

Workaround:

Instead of 

  txtMask1.Focus();
  txtMask2.Focus();

Use

  txtMask1.Focus();
                Dispatcher.BeginInvoke(new Action(() =>
                    {
                        txtMask2.Focus();
                    }), DispatcherPriority.Loaded);

Currently, the SpinMode logic tries to kick-in on MouseWheel, even if the control is not focused. This handles the event which causes unexpected behaviors in some cases. Do not handle the MouseWheel event when the focus is not within the masked input control. You can consider adding a mode that allows you disable the default behavior.

Initially, when the value is 0, the mask control could look like - $__,___.00 instead of $__,___0.00.

Setting the Extnesions Minimum and Maximum values restricts the input of values that fall in the designated area but that start with a digit lesser than the minimum value. For example in the MaskedNumeric/CurrencyInput, if you set MaskedInputExtensions.Minimum="2" and MaskedInputExtensions.Maximum="20", you can't enter 12 unless the current value is 2 and the cursor is positioned before the 2 - only then you can insert the digit 1 before the digit 2 to create an input of 12.

When the Value of the RadMaskedInput (all RadMaskedInput controls) is changed in code behind, the ValueChanged event isn't fired.

When using implicit styles mechanism and you merge Telerik.Windows.Controls.Input an exception is thrown.

If the XAML file is set with BUILD ACTION PAGE the issue is not reproducible.

Another workaround is to reference dlls only, not xaml theme files.

Issue is reported in several msdn / stackoverflow threads and it appears to be an MS-TextBox one. 
http://stackoverflow.com/questions/6850713/weird-xaml-parsing-error-when-trying-to-set-textbox-isreadonly