"New" Teams meet now defaults to audio call not video call
Hello all, Just been updated to Teams version 23285.3607.2525.937 and in this version, calling other users behaviour in the UI has been changed to instead of having two distinct buttons for either an Audio or Video call, there is now a "Meet Now" button with a drop down where the main click option defaults to an audio call. This is a poor change to the UI design and I also cannot see an option to set video calls to be the default meet now option, is there an option to change the default behaviour and where is it?I want to be able to group app icons on Start menu - Windows 11
for example I want to put PWAs icons in one group, put Photo related app/software icons in another group and so on. Ideally I want to do this by dragging an icon on start menu and dropping it on another icon to form a group - Windows 11 insider Upvote in feedback hub: https://aka.ms/AAdps2rWindows 11: Turn the "Show more options" context menu into a slide down menu
Turn the "Show more options" context menu into a slide down menu and show those extra options in modern style Change the Windows 11 context menu so that when user clicks/taps on "show more options", the context menu expands and the rest of the options become visible in the same modern style with a sliding down animation, possibility with the ability for user to scroll up/down through the options (with mouse wheel or touch). Upvote this feedback in feedback hub: https://aka.ms/AAd53qzGetting Started with React and SharePoint - From a UX Designer/Developer's Perspective
If you've been keeping watch on the new SharePoint Framework you have undoubtedly read or experienced the dichotomy of extremely basic "Hello World" articles and if not basic, then articles written by hard core-code-ninja programmers. If you’re a Designer, Developer or UX Practitioner trying to make sense of the React and Modern SharePoint Framework universe it can be difficult reconciling these two very different spectra. From a UX Practitioner's standpoint we need to know enough about Development to strategically understand what's possible in Design, while attempting to make a User’s experience better. That middle ground of development and design when focused inside of SharePoint helps to build exciting experiences and promote healthy User Adoption. The goal of this 5-part series is targeted at the hybrid role of Designer, Developer and UX Practitioner in an attempt to navigate through some of the poorly documented and major hurdles of React Development. Part 1 – CSS tricks and working with syntax Part 2 – Integration of third party or legacy plug-ins Part 3 – Images, SVG graphics and Components Part 4 – REST call to a SharePoint List and displaying the results Part 5 – Building a super cool React Modern SharePoint Web Part React SharePoint Modern Framework Web Part – we will be building this in Part 5 of this series. Alright, enough talk let’s get started. Part 1 CSS in React Ok so if you’re like me and have been using traditional CSS for almost 20 years, CSS inside React at first... is a little painful. There is an in-depth blog post written by Agata Krzywda about CSS and React https://codeburst.io/4-four-ways-to-style-react-components-ac6f323da822 detailing almost every situation and use case. The article mentioned by Agata is very helpful for understanding CSS and React, but what the article doesn’t take into account are the real-world syntactical oddities that we run into on a daily basis, which like I’ve mentioned are generally missing from 80% of online React documentation. The SPFX team at Microsoft has done a great job by giving us the SPFX boiler plate webpart that generates the code below. Deciphering the CSS in the SPFX boiler plate has a pretty steep learning curve partially because the boiler plate project hides some key ingredients that if you are not outwardly looking for them, you'll miss out on the learning experience. Example the Office Fabric .css file is buried in the node_modules folder and is not referenced through import in the head of the page... so if you were trying to understand where "ms-bgColor-themeDark" is being referenced its completely confusing... Let's take a look at Lines 11, 14. Line 11: <div className={`ms-Grid-row ms-bgColor-themeDark ms-fontColor-white ${styles.row}`}> Line 14: <div className={"ms-font-1 ms-fontColor-white"}> These two lines show different ways to use CSS in React that mimic 90% of the web at large. Now Let's look at Line 16. Notice there's some different stuff going on here... "styles" is the imported reference to the scss file and "label" is the class name. Line16: <div className={styles.label}> * The big take away here is that CSS in React has multiple ways to use it, and you can choose which works best for you depending on your situation. Below are some extremely useful and hard to find syntactical variations of CSS in React, that go beyond the CSS article written by Agata and that also extend the SPFX boiler plate example from Microsoft. Here are a few super helpful examples of className syntactical combinations Multiple class names with hyphens concatenated together while still referencing the import iconstyles module. className={[iconstyles["glyphicon"], iconstyles["glyphicon-star-empty"]].join(' ')} Entire string of static classes in a string with a variable name inside the string <div className={`ms-Grid-row ms-bgColor-themeDark ms-fontColor-white ${styles.row}`}> Multiple static classes along with a variable name concatenated together className={[`mix`, `all`, item.Category ].join(' ')} Class name as a static string. Notice the use of this ( ` ) not ( ‘ ) or ( “ ) className={`mix`} Class used classically in a variable as larger static string const htmlstring = ` <div class="row mixitup-wrapper"></div>`; This table hopefully saves a fellow Designer, Developer or UX Practitioner some time and effort, I know while I was picking up React each variation of CSS was a watershed moment. In Part 2 of this series we are going to hammer out how to work with third party plug-ins inside React like JQuery, Bootstrap and MixitUp.UI/UX problem in Edge with RTL languages (Right to Left)
notice anything strange? the place of Edge side bar and vertical tabs is changed when you use a language in Edge that supports Right-to-left. this is very annoying. I want to use a language that supports RTL but I don't want the location of everything in Edge to change. it's not just these 2 elements, everything in Edge UI changes. the location of tabs, the address bar, favorite bar, the menu, everything. there really needs to be an option to keep Edge in Left-to-Right format (LTR) and still use any language we want in Edge, it's a must have. the location of buttons and UI are something that I'm used to, when it becomes RTL, everything goes haywire and I get lost. I'm sending this using feedback button on Edge, if you happen to be using a RTL language or know it, please try it and send a feedback from your browser too. let's get this fixed.Bring back the ability to hold Shift + click on pinned icons on Taskbar to open multiple instances
Bring back the ability to hold Shift + click on pinned icons on Taskbar to open multiple instances of the app Windows 10 has this useful feature but it's missing in Windows 11, where you could hold Shift and then click (left-click) on a pinned app icon on taskbar that is already open, in order to open another instance of the app. for example the file explorer, browser, media player, text editor, calculator and so on. Upvote in feedback hub: https://aka.ms/AAdps2n
Build a unified Windows UI experience
https://techcommunity.microsoft.com/t5/discussions/top-feedback-summary-for-january-12/m-p/2053932 As shown in the link, the introduction of transparency effects for Microsoft Edge dominates the rankings all the year round. Obviously, users are so looking forward to acrylic and fluent design! With the continuous development of FDS, the transparency effect is no longer the focus. We know that using Navigation in XAML will no longer enable the transparency effect of the underlying window by default, and the default transparency effect will remain in the window of this layer. The difference is shown in the figure In this picture, the window title bar and toolbar of "Screenshots and Sketches" are transparent to the desktop and windows below In this screenshot of the Microsoft Store, the elements at the bottom of the window are transparent At present, it seems that the design team intends to adopt "transparency to the elements in the window" as a trend, and will not develop more transparent title bars and side bars in the future. Therefore, the focus is not on transparency, but on other areas. Microsoft Edge now gives me the feeling, as if I changed the Chrome icon to Microsoft's, and then told me, look, this is Microsoft's browser. I think this is a huge irony and tragedy for the visual perception of the Microsoft brand, which means that users cannot really recognize the work that Microsoft is doing on this browser, and-let users understand that this is a different version of Chrome Browser. Microsoft must use practical actions to reshape Microsoft's brand image. I think the core action is to use native controls, or reshape the appearance of non-native controls that look like native controls. This includes the following: 1. Forward and back buttons, refresh buttons, address bar and toolbar 2. Context menu 3. Edge's special pages, such as settings, downloads, favorites, etc. For the address bar toolbar area, I think it’s not too difficult to build the appearance with XAML (or WinUI 3). If it is difficult, it is not too difficult to make these controls look like Windows. This area should look exactly like the old version of Edge. The context menu is a place where it is easy to achieve a smooth design. I think it is nothing more than adding a transparency, adding a matte, adding a noise, adjusting the kerning and line height, and finally adjusting the edge and projection. I don't think how difficult it is, is it really difficult? Or, will you consider WinUI 3 release? Or use XAML island, just like the old version of Edge? Is this really so difficult? I can't understand why I can't do it after a year. I think any user will notice the huge difference between the sidebar of the settings page and the sidebar of XAML Navigation in "Windows Settings". I don’t want to worry about whether the highlight bar is a rounded rectangle (capsule) or a right-angled rectangle-because Both are FDS, but there is no lighting effect (CompositionLight Class), completely different spacing, inexplicable margins, lack of transparency, all of which remind users that this is a web page, not a native one. UI-based application. It seems to have nothing to do with the Windows design language-although it seems that many applications have to do this, indeed, cross-platform, Web development also meets Microsoft's strategic goals, it is really difficult to resist the temptation. Skype, Microsoft Teams, and Outlook to come,-and the latest file explorer used on Windows 10X, the design looks increasingly unrelated, each team has its own ideas, compare , The unification of macOS is simply outrageous! I implore the development team to read this article to help users build a harmonious and unified appearance, One Windows, One Microsoft https://medium.com/microsoft-design/fluent-makeover-photolab-a583d25f362bAdd "Disable Extension" option to the right-click menu on extension Icon in Edge toolbar
There is place for 1 more option and it's "Disable Extension". it's a tiring task to go to the ellipsis menu, then extension, find the extension and disable it. just add that option to the right-click menu on extension icon in Edge toolbar. there is this less used option "inspect pop-up window" that appear for all extension icons, so just remove it or hide it and replace it with "disable extension" option. Thank you!
