[Wayland] PWAs no longer appear as separate app windows — all group under main Edge icon
Hi, Since around 2025-09-07 to 2025-09-10, I’ve noticed that on GNOME (Wayland) all installed PWAs (even across different profiles) now appear grouped under the main Edge browser icon in the GNOME Shell dash/taskbar. Previously, each PWA would open in its own window group with its own icon. This is still the behavior in Chromium/Brave/Chrome, and can be restored there by editing the PWA’s .desktop file to set: StartupWMClass=<same value as Icon> However, Edge now seems to ignore StartupWMClass completely on Wayland, breaking workspace separation and making task switching hard. Environment: Ubuntu 25.04 GNOME 48.0 / Mutter (Wayland) Kernel 6.14.0-29 Intel Iris Xe GPU Edge (latest stable, observed post 2025-09-13) Repro steps: Install any PWA (e.g. Outlook, Teams, Spotify) from Edge Launch it (from any profile) Observe that it appears grouped under the main Edge browser icon Expected: PWA shows under its own icon and window group like in Chromium-based browsers Actual: All PWAs are bundled into the main Edge window group Editing StartupWMClass in the .desktop file no longer helps This regression makes PWAs much harder to manage on Wayland. Please route to the Linux/Wayland team if possible. Thanks!Mica issues again (title bar + context menus)
Weird bug again - in both Stable/Dev the title bar mica effects are not working, but the dropdown & context menu (three dot settings) is. In Canary, the title bar mica effect *is* working, but the dropdown/context menu is not (solid white). I reported via feedback as well. Canary: Dev/Stable:
MS Edge - Sidebar and copilot not working on Linux Ubuntu v24 LTS
Sidebar not syncing or accepting new app additions (+). Copilot button is dead/inactive. Sidebar settings are well configured. Using the latest version of the Ubuntu OS and MS Edge. Functionality appears to be absent as product was released without full functionality....Lame!
Synchronization issue
I have an active Microsoft 365 subscription. My wife and I share Microsoft To Do lists. We recently noticed a synchronization issue: When she creates/deletes/updates tasks, they sync to me. When I create/update tasks, they don’t sync to her. When I delete tasks, they are deleted for her. We’ve already signed out and back in, and tested on different devices and platforms. Permissions are correct, and everything used to work before.
Problem with the option to prevent customers managing their bookings
We have used Microsoft Bookings for several years to let our customers book services with us but we're noticing a trend that the customers tend to rebook their appointments an excessive amount of times which often leads to available spaces on group bookings being wasted. It also increases the admin time because each rebooking needs to be processed again so that the necessary preparations for the customer can be made. One idea we have to try and keep things under control would be to say that the customers should only book the service one time so that we can administer their bookings one time only and then if they miss their appointment time they could just "drop-in" because all the necessary preparations would have already been made for them. But I don't think this will change the behaviour with how the customers keep moving their bookings. What we really need is the option to prevent the customers from cancelling or rebooking their times themselves. I am aware that there is an option to "Let customers manage their appointments" but this feature seems to be broken! To disable the option you have to go into the calendar and select the group booking. In the pop-up window underneath the "Added Customers" you can disable the option to prevent the customers from managing their appointments. When you do this it takes away the reschedule and cancel buttons but it only works as a temporary measure because as soon as a new person books a place on the same group booking then the option becomes automatically enabled again! Then all the previous customers can also see the reschedule and cancel buttons again. It feels like this part of Microsoft Bookings is broken and unusable at the moment. The only way I could imagine it working at the moment is if a group booking runs out of free spaces and then nobody else would be able to book a place so if you manually disable the option at this point then would remain disabled for everybody. But until the appointment time runs out of spaces then people are just going to keep moving their bookings around. You could probably keep manually disabling the option when new bookings are made but this also adds to the admin time and it doesn't seem like a very practical workaround. Another idea we have had is to set a longer "minimum lead time" because this is another way to prevent people from cancelling and moving their bookings but it reduces the flexibility of when the services can be booked. But we're actually going to try this idea and see how it affects things along with changing the information to try and make the customers aware that they are being restricted to one booking. We hope that the option for the customers to manage their own bookings gets fixed soon. It also does not make much sense that it needs to be disabled per booking in the calendar? Shouldn't this be a feature that applies to every booking for a service instead? I've tried to disable the option on two different booking pages but the experience is just the same, the option just becomes automatically enabled again when a new booking is made.
Teams v2 - Meet Now says 'Meeting Ended' in channel
Our org fully switched to Teams v2 last week - IT had been using it for the most part for ~2 months with no issues. Yesterday we started getting tickets from users that use the Meet Now functionality in their Team's General channel to have impromptu meetings throughout the day. On Teams v1 someone would start the meeting, and everyone else in the channel would get a toast notification that a meeting had started. If they missed the toast they could go to the channel and click 'Join'. In Teams v2 people are starting Meet Now meetings in the same channel, but no one is getting a toast notification, and when they asked people to join via chat, people would go to the channel and the meeting says 'Meeting ended'. Except, when they close and relaunch Teams v2, they can suddenly join the meeting. The bug is not apparent in either of the web versions of Teams either. Screenshots of behavior: https://imgur.com/a/x6viQ4j I've opened a ticket with Microsoft (2311280010000070) and I'll keep everyone posted on that, just wanted to see if anyone else was affected. A lot of our users are saying closing and relaunching Teams v2 breaks their workflow and want to switch back to Teams v1.
