Universal Windows Platform

Welcome to the Universal Windows Platform Developer Feedback site. This site provides the Windows developer community with a channel for feedback on the following topics:

  • Windows developer platform (APIs, runtimes, and controls)
  • Dev Center (dashboard, reporting/analytics, submission process, etc.)
  • Microsoft Store

Your suggestions will be reviewed by the Windows platform developer team to help with planning ideas and to better understand how developers are using the platform.

What this forum is not intended to cover or capture:

  • Windows consumer suggestions: Use the Windows Feedback Hub app built directly into Windows 10
  • Documentation on docs.microsoft.com: Sign in at the bottom of the page to give documentation feedback via Github
  • Visual Studio / .NET: Use the Visual Studio UserVoice site

If you’re new to UserVoice, two things to keep in mind are (a) List items (and item rankings) represent community interest in features, and not the actual priority list for the product team; and (b) Suggestions made using this forum will be moderated if they do not actually represent a feature request (or if too many different ideas are included in one suggestion).

How can we improve the Windows dev platform?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow C# style boolean conversion with x:Bind

    With x:Bind we can invert a boolean property with a ValueConverter like this:

    Visibility="{x:Bind IsLoading,Converter="{StaticResource BooleanInverseConverter}"

    But wouldn't it be much cleaner for that widely used boolean case to write just this:

    Visibility="{x:Bind !IsLoading}"

    To generated the code should be possible, and also to check in that generation whether IsLoading is a boolean or not. Even without checking, it won't compile if IsLoading wouldn't be a boolean, which is fine.

    Thanks,
    Thomas

    54 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  2. Virtualized RichEditBox

    Currently the RichEditBox (or even the RichEditBlock, or even the TextBlock) are not virtualized. As a result with a moderate amount of runs in the box it becomes almost unusable slow near 4000-5000 lines.

    The request is, create a virtualized RichEditBox that is capable of handling large files.

    7 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  3. AutoSuggestBox should have SelectAll() method like TextBox

    In UWP, TextBox has a method called SelectAll() that selects all the text in the Text property of the TextBox control. AutoSuggestBox should have the a method that performs the same action.

    8 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  4. TextBlock should not be sealed

    Sealed classes fly in the face of OOD, so there should be an incontrovertible reason for making a class sealed. I don't accept the rational that sealing the class makes it perform better. If you don't want the performance hit of virtual methods, then don't make them virtual. There's no justification for sealing the entire class.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  5. The SelectedNodes property for single-select TreeView control

    The SelectedNodes property for a single-select TreeView control should always have 0 or 1 item in the list. This would be consistent for node selection in the control, except that in single-select mode, the list can have a maximum of 1 item.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  6. Universal XAML

    Universal XAML - Embrace UNO UWP and extend it.

    Make possible for Developers to use the same XAML dialect on Web, Mobile, Desktop and IoT Applications

    Also make all this work with all .NET languages, including F#

    4 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  7. print page sizes

    Within UWP - The ability to manually and fully configure the page size output. Not use the ENUM mediapagesize, but something like WinForms where the specific page size can be selected.

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  8. Allow TextBox Cursor to be something other than I-Beam

    Currently the only way to set a new cursor is on the Window.Current.CoreWindow.PointerCursor instance. Unfortunately, the TextBox control overrides this setting even if the control is ReadOnly or Disabled. The TextBox is a standard ListItem element and when using them to display lists of items it's not user friendly to change the cursor to an I-Beam when in fact the user cannot enter any text and the application simply wants the user to scroll through the list as in the following example:

    <RelativePanel x:Name="thisRelativePanel">
    <TextBox x:Name="thisTextBox" Text="Hello" KeyDown="ThisTextBox_KeyDown" IsReadOnly="True" PointerEntered="ThisTextBox_PointerEntered" PointerExited="ThisTextBox_PointerExited" />
    </RelativePanel>
    private void ThisTextBox_PointerEntered(object sender, PointerRoutedEventArgs e)
    { …

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  9. SwipeControl should support mouse input

    The SwipeControl control should support mouse input as well as touch input. Currently it only supports touch input.

    I appreciate that swipe controls have come out of developments around touch interfaces. However on a platform that allows for a single app to run on both desktop and touch devices I think that users will be expecting to be able to interact with the app in similar ways across devices.

    Microsoft have set precedent for this in their own apps. Outlook for example utilises a SwipeControl type arrangement (that can be interacted with using a mouse) for marking emails as read…

    27 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    6 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  10. UWP Grid should have ShowGridLines property from WPF

    The WPF Grid control had a ShowGridLines property. This is helpful for layout debugging. This property is missing in UWP.

    18 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  11. Modern Windows UI in Win32 desktop applications

    Bring modern Windows UI to existing Win32, WPF and Windows Forms desktop apps with the option to adopt islands of Windows.UI.Composition and Windows.UI.XAML content incrementally. Allows desktop apps to incrementally adopt UI innovations and creates a bridge to UWP for app UI.

    384 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    88 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  12. PlaneProjection

    PlaneProjection with Storyboard animations is presently unusable when any of the Rotation properties are applied (RotationX, RotationY, RotationZ).

    If you have code like this:
    storyboard.AddAnimation(img, duration, oldpp.RotationX, rotationX, "(UIElement.Projection).(PlaneProjection.RotationX)", ef);
    storyboard.AddAnimation(img, duration, oldpp.RotationY, rotationY, "(UIElement.Projection).(PlaneProjection.RotationY)", ef);
    storyboard.AddAnimation(img, duration, oldpp.RotationZ, rotationZ, "(UIElement.Projection).(PlaneProjection.RotationZ)", ef);
    storyboard.AddAnimation(img, 800, 0, 200, "(UIElement.Projection).(PlaneProjection.LocalOffsetX)", ef);

    storyboard.Begin();

    followed by

    … setup code then

    storyboard.AddAnimation(img, 800, 200, 0, "(UIElement.Projection).(PlaneProjection.LocalOffsetX)", ef);

    You get a bounce in the in animation with the resulting end point of the animation being incorrect.

    This used to work. It's a horrific bug that was introduced with an OS change and affects windows 1703 and above.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  13. Reveal Highlight Dropped Frames

    In recent 19H1 builds, particularly 18329, the reveal highlight effect will occasionally drop frames when users hover over supported controls.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  14. TreeView event for child re-ordering

    The UWP TreeView control lacks an event to notify that child nodes have been re-ordered due to a drag and drop. The DragItemsCompleted event is fired but there is no direct information in the arguments about whether the child ordering has changed or whether a child has been added.

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support Random Access in ListBox, ListView, and GridView

    Currently the ListBox, ListView, and GridView controls only notify their ItemSource when the user scrolls down to indicate that the underlying ItemSource object needs to add more items to the control's list. In other words the only supported access is sequential.

    Random access requires that these controls notify the ItemSource when the user scrolls up as well as down. Plus, allow the user to select a random item for example via a vertical scrollbar.

    Minimum Required Properties:
    Get/Set ItemCount - this is the total # of items in the ItemSource
    Get/Set ItemIndex - this is the first item of the…

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  16. Provide a way to disable Pivot animations

    Just like how we can disable ListView animations by setting ItemContainerTransitions to null, for example.

    1 vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  17. UWP Timepicker suppor various type of time formats

    Allow to set in timepicker various type of time. For example H:mm:ss or only hours and UI of control will reflect theese formats.

    2 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  18. MediaTransportControls do not auto-hide correctly

    MediaTransportControls no longer auto-hide correctly for UWP apps on desktop when using the mouse pointer. When the pointer is used to click the play/pause button, the transport control bar begins to hide and then immediately pops back up again. This bug does not occur with a game controller.

    This appears to be related to the introduction of MediaTransportControls.ShowAndHideAutomatically property in Build 16299.

    I am using Windows v1809.

    This bug is reproducible in any app which uses the transport controls, including the XAML Controls Gallery app (under Media) available in the MS Store. The link to the app can be found…

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  19. Xamarin.Forms - Prevent keyboard from showing on Entry field focus

    Currently, Entry field in Xamarin.Forms provides no functionality to prevent soft keyboard from showing up entirely. There are solution out there that will hide it but they make things even worse since now you have keyboard popping up briefly, then disappearing from the screen.

    It feels like having a way to disable keyboard from showing up entirely on an Entry field makes sense. For example, I make my own buttons, that resemble keyboard. Tapping on each of these, puts some characters in the Entry field without showing keyboard but only when Entry field receives focus.

    Another example, scanning with external…

    3 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
  20. Select Treeview node from code

    The TreeView (from Windows Update 1803) lacks the possibility to select a ceirtain TreeViewNode from code.

    For example an "IsSelected" property could be added to a TreeViewNode or a function like selectNode(TreeViewNode) to the TreeView.

    11 votes
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  XAML/Controls/Composition  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 14 15
  • Don't see your idea?

Feedback and Knowledge Base