Custom settings item. However, let me set an expectation that this is not something we have a priority from design discussion perspective. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. I think the lack of Acrylic is ridiculous, and a simple inset shadow (as mentioned in a post here: #1291) could potentially solve the problem of distraction, by making it seem as if the pane on the right is in the front. Otherwise, register and sign in. NavigationView is a conscious control. Use AcrylicBrush, get Fallback colour. UI Fabric will not be using acrylic and will continue to use solid greys. Nor do I have any real influence over what apps (created by other teams at Microsoft or 3rd-party) have chosen to implement. We use essential cookies to perform essential website functions, e.g. Learn more.
Might as well just use acrylic. Why shouldn't some kind of acrylic be used if it's available? (Like with Settings, Alarms + Clock, To Do, Mail + Calendar, etc). So, to my understanding, it should be reasonably assumed that the overwhelming reason why this was changed was a change in direction for when to use acrylic based on the visual aspect. First published on MSDN on May 06, 2018 The navigation view control provides top-level application navigation. (Note: I used the Windows Dark Theme for the system and apps.). This control is designed to … Where does this data come from? For more information, see our Privacy Statement. Acrylic (and with that "fauxcrilic") was ruled out for the non-transient NavigationView pane because it was suggested to be "distracting" among other things. The latter background acrylic "blocks out" much more of the background than the former does yet it's still enough to not produce a solid and boring looking single background color. I just wanted to draw a comparison between the two. they're used to log you in. However I can’t see the separator. Therefor, a lot of apps statically override this accent color. Have a question about this project? technical support services. The need for a fallback makes sense on low powered devices, but is arguably more distracting on a desktop PC which has the power available to use the effect on all windows. So I'm not seeing how "fauxcrilic" should come into play here. :). The Settings app's sidebar is not the standard NavigationView sidebar, which is why it still uses Background Acrylic. If you want to 100% draw attention to the panel on the right, why not re-add the BG Acrylic, then add an inset shadow to the NavigationView when in expanded mode by default so it makes it look like the main pane on the right is in front?
You can follow the question or vote as helpful, but you cannot reply to this thread. I'll be sure to bring up your points when the time is right. privacy statement. This conversation about the choice of grey should probably be tackled by looking at all colours used as defaults from everything to content backgrounds, to Titlebar colours. Microsoft has the resources to run usability studies, and to do A/B testing with users in apps. Please take us seriously. By default, the system accent color is the Windows theme color chosen by end user. You signed in with another tab or window. I have added the separator by setting group id in menu. @Felix-Dev With Apple doubling down on their translucent sidebars in iOS and macOS - maybe Microsoft can be persuaded to change this default - until then, I will always push for it (and a less 'distracting' tint than the 60% used for settings. You can use the following resource and put it in the Page.Resources. Agree 100%. UI Fabric doesn't have acrylic in its Nav View because it doesn't support it. Already on GitHub? Add the shell’s Acrylic to NavigationView. I guess it is because the separator color is same as the background.
UI Fabric will not be using acrylic and will continue to use solid greys.
Design is often subjective, and is not something that can be entirely driven by data and telemetry. That's why we do not want to be making any changes to this until other, higher priority design discussion settles and sets the right directional decisions. Neither of those windows were in focus. Not all of us do. So I've suggested a solid color that hopefully feels less random and less drab than the current NavigationView implementation and better aligns with other Microsoft controls frameworks. Sign up for a free GitHub account to open an issue and contact its maintainers and the community. I implore MS (@YuliKl, @chigy) to consider the Windows Shell Flyout Background Acrylic for the Navigation View pane because it a) addresses the complaints by MS (the background "shine through" effect is so faint that there really isn't anything distracting or attention inviting by it) yet b) also gives us Windows 10 aesthetic lovers and Fluent Design fans something to still look forward to with this change. Hopefully a case can be put forward for reconsidering Acrylic. Using the NavigationView in your UWP applications, http://schemas.microsoft.com/winfx/2006/xaml/presentation, http://schemas.microsoft.com/winfx/2006/xaml, http://schemas.microsoft.com/expression/blend/2008, http://schemas.openxmlformats.org/markup-compatibility/2006. I'm trying to work within the constraints of the design system as I understand them. Thanks for your feedback, it helps us improve the site. I just want to point out the differences between XAML Controls Gallery and Settings. Also, an inset facing shadow and a lighter color would be another way to direct users' attention to the right. While we are not at all perfect yet, but we are working to be more data driven when it comes to design decisions and changes and trying to understand where your rationale are coming from. With this option in place, performance shouldn't be the reason to remove acrylic as the default non-transient pane background for the NavigationView. It is darker than the white, and Acrylic was too, except the white background is the same material (or lack of) as the grey pane, therefore the attention is drawn to the grey pane. We were experimenting with a new design direction that didn't work out. We totally understand what you’re saying, but if you are just a program manager and designers never speak on here, then what is the point of even having this GitHub issues page if they can never be fixed? Connect and engage across your organization. With the Acrylic, it was a different material than the plain white so the attention was drawn kind of not to a specific place, because the white was important, because of its brightness, and the Acrylic was also important, because of its different material. Speaking of Apple legitimising UI, now Apple is getting Widgets (Live tiles) maybe Microsoft can row back on that decision in 10X. I will try! Add a single “TextBlock” element to the “Grid” element in each page. Also, i'm gonna kill two birds with one stone and also say that I think there should be an option for high end PC to have acrylic visible for all windows and not just the active one (I know that the reason for not being always visible was for performance, but I'd be willing to take that hit for a more pleasant interface). Learn more, We use analytics cookies to understand how you use our websites so we can make them better, e.g.
Microsoft global customer service number. Performance and some perceived distraction are the reasons it was removed. Oh and a recommendation for all apps like Your Phone, to extend into the titlebar! Empowering technologists to achieve more by humanizing tech. official This fauxcrilic would be a fallback between full live Acrylic, and the Solid Colour, and need not be a temporary fill in, but a performance option. XAML Islands is a new technology that allows loading UWP controls in non-UWP desktop applications, such as WPF, Windows Forms, MFC. Also I think the idea about the titlebars is definitely something Windows needs. Fully managed intelligent database services. I feel there must be a deeper reason than performance alone, because there must be a way to improve performance, it seems so unlike the WinUI team to simply give up on something so huge like this. In fact, the used background acrylic there has a much "weaker" effect than the effect of the background acrylic in the Setting app. I really think that Felix's idea is a good compromise, specially since when in Dark Theme with a really bright background (or the opposite) the current acrylic background of the NavigationPane is too eye catching, and so taking attention that should be on the Content. We use optional third-party analytics cookies to understand how you use GitHub.com so we can build better products. Successfully merging a pull request may close this issue. The following code, added to the constructor of your main page, can help extend your views into the titlebar region.