[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!
Latest Stable Linux build of Edge crashes when I download something.
When I download something from the internet and When I click save as the browser crashes, using RPM linux build on Fedora and using the latest stable version at the time of writing this discussion version Version 143.0.3650.139 (Official build) (64-bit)
New Outlook: Shadow contacts not stored in Outlook.com, no sync/export and missing Birthday calendar
I’m reporting a reproducible data‑integrity issue in the New Outlook for Windows that affects Outlook.com contact storage and synchronization. 🔍 Summary When a contact is created in the New Outlook, the client appears to save it successfully. However, the resulting contact is not stored in the user’s Outlook.com account as a normal cloud contact. Instead, it becomes what I would describe as a local “shadow contact” in the New Outlook cache. ⚠️ Observable Behavior • The contact appears in Outlook.com → People, but does not show “Stored in: Outlook” • The contact does not appear in Outlook.com CSV exports • The contact does not sync to mobile devices connected to the same account • The contact does not populate the Outlook.com Birthday calendar • The contact is lost if the New Outlook app is reinstalled or its local store is cleared 🧪 Steps to Reproduce 1. Open the New Outlook for Windows 2. Create a new contact and add a birthday 3. Save the contact 4. Open Outlook.com → People 5. Locate the contact — it will appear, but the “Stored in: Outlook” field is missing 6. Export contacts from Outlook.com (CSV) — the contact will not be present 7. Check a mobile device configured with the same Microsoft account — the contact will not be present 8. Check the Outlook.com Birthday calendar — the birthday will not appear 9. Reinstall the New Outlook app — the contact will be gone ✅ Expected Behavior • Contacts created in the New Outlook should be stored as first‑class Outlook.com contacts • They should appear with a proper “Stored in: Outlook” location • They should sync across devices, export via Outlook.com, and populate the Birthday calendar ❌ Actual Behavior • Contacts created in the New Outlook are effectively “shadow contacts” stored in a local cache • They look normal in the New Outlook UI, but they are incomplete, non‑synchronizing objects from the service’s perspective 📉 Impact • Silent data loss risk for users who assume contacts are in Outlook.com when they are not • Inconsistent contact and birthday data across devices and services • Split contact store model: • Real Outlook.com contacts • Local shadow contacts created by New Outlook 📎 What I’ve Already Done • Submitted feedback through the New Outlook (Help → Feedback → Report a Problem) • Submitted a detailed report via the Windows Feedback Hub • Contacted Microsoft Support, who advised that escalation must occur via Feedback 📣 Request I’m posting this here to document the issue publicly and to ask: • Can anyone from the Outlook / Exchange / Outlook.com team confirm this behavior? • Can other users reproduce this with the steps above? Given the data‑integrity implications, I’m hoping this can be brought to the attention of the relevant engineering team. Any confirmation, additional data points, or official guidance would be appreciated.
Microsft teams wont minimize on endevourOS (arch based)
Not sure if this is the correct place to put this since its my first time using this site but here we go Teams wont minimze when minize is pressed. Ive installed the Gnome look and added minimize, resize and close buttons to the install via cli Ive disabled boot on startup and keep running when closed if that matters
New Outlook Randomly Assigning/Overriding Categories to Calendar Items
I use Categories to color code and organize my calendar. In the New Outlook, the system is randomly assigning categories to some of my calendar items. For example, I have one item that has no category assigned, but now it uses my "Misc Meeting" category. Another one I'd already labeled with the "Analyst Team" category and now it's added "Phone Call" to the item (which is making the wrong color display). In both of these examples, if I right click to access the categories and correct them (or even just "Clear all categories"), once I submit, after a few seconds the incorrect category labels and colors come back. Help?
Video Super Resolution Missing Options in Setting
Enhance videos in Microsoft Edge (Flag: #edge-video-super-resolution) is missing critical options in setting, making it impossible to function properly. In Version 136.0.3240.29 (Official build) beta (64-bit), as well as the previous beta build, it is missing the option to choose from three methods of video enhancement, as shown in screenshot. Here is the setting from latest beta build: This is how it is supposed to look: Thus, beta build defaults to Microsoft Super Resolution and I can't find a way to use graphics driver enhancement like RTX Super Resolution, which is critical to my experience. Also, HDR is no longer supported when video enhancement is enabled, which I believe is a limitation of Microsoft Super Resolution.
Critical Pen Hover & Stray Ink Issue on New Surface Pro 11 for Business with Slim Pen 2
Hello Microsoft Community and Support Staff, I am writing to report a critical and seemingly widespread issue with the pen input on the brand-new Surface Pro for Business, 13-inch (Intel model, often called Surface Pro 11 "Luna Lake"). The Core Problem: Pen Draws Without Touching the Screen When using the Surface Slim Pen 2, the device begins to register ink input while the pen is still hovering a few millimeters above the screen. It does not require any physical contact or pressure. This "hover-inking" makes handwriting completely unusable. As I write, any time I lift the pen to start a new letter or stroke, the pen continues to draw a line as it moves through the air to its next position. This results in messy, connected handwriting with unwanted "tails," completely defeating the purpose of having a premium inking device. This is Not a Defective Unit - It's a Replicable Problem Initially, I thought I had a faulty device. However, to isolate the issue, I have performed extensive testing: I have personally tested this on [3] brand-new Surface Pro 11 (Intel) devices. I have used [4] different Slim Pen 2s. The exact same hover-inking problem occurred on every single combination of device and pen. Furthermore, I have already performed all standard troubleshooting steps, including: Clean OS installation via Surface Recovery Image. Ensuring all Windows, driver, and firmware updates are installed. Running the Surface Diagnostic Toolkit (which reported no errors). However, the same issue continues to occur even after trying these methods. Additionally, it has been reported that the issue also appears on the latest Surface Pro 12-inch model with the Snapdragon X Plus, just like on the Surface Pro 11 that uses the Qualcomm Snapdragon X Elite instead of Intel’s Lunar Lake. (I do not own any Snapdragon devices myself. If you own a Snapdragon device and are experiencing the same issue, please share your feedback.)" Video Evidence: I have recorded a clear video demonstrating the problem. It shows the pen drawing while hovering on the Surface Pro 11 and makes unwanted tails on handwriting letters. Video Link: https://youtube.com/playlist?list=PLG_7BXFA-cL4evqe0RmRz--iFjDC1HVgT&si=EmEypaAqSyRozr67 Questions for Microsoft: Is this a known issue with the new Surface Pro 11 (Intel) model's firmware or drivers? What are the official steps to escalate this issue directly to the Surface engineering team for a fix? This is a major flaw in a flagship product that severely impacts its core functionality. I have submitted a formal bug report through the Feedback Hub, which can be found here: Feedback Hub Link: https://aka.ms/AAxzh27 I urge the Microsoft team to investigate this with high priority and release a firmware or software update to recalibrate the pen's Initial Activation Force (IAF). Thank you for your attention to this serious matter.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!Bug: Empty bar at bottom of screen on Android 14 Honor 70 / MagicOS 8.0
After updating Microsoft Edge to version 142.0.3595.66 on Android 14 with MagicOS 8.0 on an Honor 70 smartphone, a permanent empty strip appears at the bottom of the screen when using gesture navigation. This issue was not present in previous versions, such as 141.0.3537.99. Disabling the "Edge-to-edge Everywhere" or "Edge-to-edge Tablet" flags does not resolve the problem. It seems to be related to the new edge-to-edge design introduced in the latest update. Please fix this issue or add an option to disable the bottom padding. Thank you.
