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.

Placeholder is set to " " and the SelectionOnFocus is set to CaretOnBeggining. When the Mask receives the focus, the caret is under the MouseClick position, not in beggining.
After load and clicking in the center of the MaskedInput , no value can be inserted.

The xaml team recently reviewed the status of this issue and won't be addressing it in future. 
Placeholder set to string.empty or ' ' should be considered not supported. Please consider using Mask="" (no-mask) instead.

The minus key on a Mac keyboard, doesn't toggle the sign of the values in the MaskedNumeric/CurrencyInput controls. However, if an external usb keyboard is attached to the machine, it can be used to toggle the sign as expected.

In a DateTimeMaskedInput with Mask=hh:mm tt, if the value is 10:00, the user can't enter 04:00.
=============
Reason for decline: The pattern "hh:mm tt" cannot accept time of type "00:00". You can test this with DateTime.ToString() method which will return "12:00" if you give him time (0hours, 0 minutes) and pattern "hh:mm tt". When typing 0 in the begging of the MaskedDateTimeInput , the control automatically converts 00:00 to 12:00 which is expected.

Workaround: You can use Mask="HH:mm tt" or Mask="t".

We have a RadMaskedCurrencyInput control defined as:
<telerik:RadMaskedCurrencyInput Margin="20" Culture="se-SE" Placeholder=" "/>.
If we focus the control and press the LeftArrowKey, the cursor is placed on the last (far right) position in the control which is incorrect.
=====
Reason for deletion: You can consider Placeholder = " " as a risky setting that might lead to unpredicted parsing results. We highly encourage you to avoid using it. Instead you can use no-mask. In this scenario you can use:

 <telerik:RadMaskedCurrencyInput Margin="20" Culture="se-SE" Mask="" FormatString="c2"/> 

Change the x:Key of the PreviewInputTextBox style in all themes definitions as at the moment it matches the x:Key of the TextBox style in the System.Windows.xaml.

This is completed in R2  / R3 2013.

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 the Currency and NumericInput controls, clear the sign of the value on SelectAll in order to allow the user to enter a negative value again. At the moment when everything in the controls is selected, the minus key only toggles the sign of the value. Instead you should be able to select a negative value and replace it with another negative value by entering the minus key and the new value.

MinusKeyCustomizations demo is added in our SDK: https://github.com/telerik/xaml-sdk/tree/master/MaskedInput/MinusKeyCustomizations 

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.

The MaskedNumericInput control doesn't escape formatting characters like 'c' or 'n'.
=============
This is not reproducible in R3 2016 version.

Implement a behavior to allow dymanically changing the FormatString precision specifier
=====
Reason to mark it Completed: Added the "Dynamic Format String" sample in SDK. Will be live with Q2 2014 (mid June)

Improve the FlowDirection functionality - at the moment setting the flow direction to RightToLeft, partly inverts the Mask value thus messing it up.

We are closing this issue as we do not think this is a bug. MaskedInput's Value , Mask and Text properties are not dependent on the FlowDirection property.
The issue the bug is originally logged to is easy to reproduce with TextBox only.
 <TextBox Text="10-Jul-2015" FlowDirection="RightToLeft" /> will produce the string "Jul-2015-10" but not the reversed string of "10-kul-2015". This is how is awpf framework implementation.

Old Name was. "Implement a feature to change the Value property based on the Text property ". However, Value is the primary property for this control and that is why we want clients to use Value property, not two-way binding of the Text property that changes the Value internally. That is why we changed the name of the feature request.

Its meaningful and clients will benefit from it. Basically clients want the literals to be included in in the VALUE. And this is meaningful only in TextInput. So new property in RadMaskedTextInput (for ex. IncludeLiteralsInValue) seems fine - Estimate 10. 

Example Scenario: 

Mask="##--##--##", 

User types 123456, Value property becomes "12--34--56" which will have the same value as the Text property.

Example Scenario:

IP Address SDK demo. Look at its code - there is converter in file and convert methods in ViewModel.cs. Both Value and Text are bound. If Value includes the dots, only 1 converter and 1 2way bingding would do the job with less code.

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

Pasting values in the controls, clears the current value in order to paste the new content

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.

We set the AutomationProperties.Name property of a RadMaskedInput control.
This property is not applied in the control (if checked with the UI Spy) the Name automation property is not the set one, but the control's value.
This forces the MS Narrator to read the value of the control instead of the desired one.

Change the InputBehavior when deleting digits after the decimal symbol: For example if the cursor position is marked with '|': Enter: 1234,56|78  (press 'del') Result: 1234,560|8 - change this behavior so that the result can be 1234,56|8.

=====

We can split the request into 2 desired results. Input: 1234.56|78. Pressing Delete

1) Produces Value 1234.5680 but NOT 1234.5608

Solution: Can be achieved with using No-Mask, FormatString and overriding MaskedNumeric/Currency Input and the protected method ReplaceChar. This is demonstrated in the attached sample.

2) (1) is True + Last zero is removed => 1234.568 but NOT 1234.5680

Solution: 2 is tightly coupled with changing the FormatString or Mask dynamically. There is no way to see number 123.456 if the Mask is "x.4" or the Mask is "" + format string is "n4". To see 3 digits only after the decimal point you need to change the Mask to "x.3" or the FormatString (in no-masked scenario) to "n3". This cannot be built-in feature because it changes a public property set by the client. So, this is custom behavior, it is also demonstrated in the SDK demo DynamicFormatString (it is pushed in GitHub with Q2 2014 Release)

InputLanguageManager does not work in MaskedInputControls
====

Reason for deletion: The bug is logged for RadMaskedTextBox and it will be removed from our suite from Q2 2014.

The MaskedTextInput Value is bound to a property whose value is modified in its setter.
 In this case the Value of the control isn't updated to the modified value of the business property.
Also if Binding Converter changes the Value, it is not updated too.
Other maskedInput controls - Numeric, Currency work in such scenarios.