Forum Widgets
Latest Discussions
Solution for PWAs not appearing as separate apps on Linux taskbars
Hi everyone, I recently Installed Microsoft Edge stable on Kubuntu Linux, and I ran into some problems using Progressive Web Applications (PWAs). Launch one Edge PWA (say, Microsoft Teams). It appears normally. Launch a second PWA (say, Microsoft Outlook). Both windows — and every PWA you launch afterward — collapse into a single taskbar group under the first PWA’s icon, identified as msedge. Pinned PWA launchers never show as running. Pinning a running PWA window produces a generic page icon that launches the bare Edge browser when clicked. Launching a PWA from the application menu briefly shows the launcher’s startup placeholder in the taskbar, which then disappears and is replaced by a separate, unassociated entry. This isn’t KDE-specific. GNOME users have also reported issues. After some troubleshooting with Claude, the issues were traced to a mismatch between how the PWAs are identified in the .desktop PWA launchers created by Edge and the app ids reported to Wayland, starting in September 2025, when Wayland was used by default. Identifier Value Example (Microsoft Outlook) Window app_id (native Wayland) msedge-_<appid>-Default msedge-_lkkahpbimdkjdjjiijflmhaeameegbcm-Default Desktop entry filename msedge-<appid>-Default msedge-lkkahpbimdkjdjjiijflmhaeameegbcm-Default StartupWMClass= in that file crx__<appid> crx__lkkahpbimdkjdjjiijflmhaeameegbcm So the solution is StartupWMClass in the .desktop launcher for the PWA to the Wayland app_id. I have a simple Bash script that will do this for all currently installed PWAs as a workaround, but the automod removed that post the last time I tried to post it. The suggested fix for Microsoft This should be a small change to Edge’s desktop-entry generation on Linux: write the Wayland app_id (msedge-_<appid>-<profile>) into StartupWMClass=, or better, make the window app_id match the desktop entry basename per the freedesktop convention. No compositor-side changes are needed — the verified workaround above demonstrates that. I’ve reported this through Edge’s in-browser feedback tool (Alt+Shift+I) with the full diagnosis. If you’re affected, sending your own feedback referencing the same details is the best way to get it prioritized — the in-browser channel is what reaches the Edge team’s triage.
CSS scrollbars
Hi, I noticed that Edge 150.0.4078.65 on Windows 11 does not appear to render the "scrollbar-color" and "scrollbar-width" styles from the https://developer.mozilla.org/en-US/docs/Web/CSS/Guides/Scrollbars_styling. See demo page: https://css-scrollbars-skobescr.yoyo.codes/, where all scrollbars appear in the default style. This surprised me for a couple of reasons: (1) "Can I Use" claims (mistakenly?) that Edge suppports this feature. (2) Other Chromium-based browsers support this feature. I'm curious if this is a regression, a deliberate product decision, or something we may expect to see added in the future.
Microsoft Graph Webhook Filtering Using Custom MAPI Properties for Weather Messages
Hi everyone, I'm working on an integration that uses Microsoft Graph change notifications (webhooks) to receive notifications for new email messages in a mailbox. Our use case is specific to Weather messages generated by our Messaging platform. Currently, we subscribe to mailbox notifications and receive events for all incoming emails, which results in significant post-processing on our side. I'm looking for a way to perform server-side filtering so that only Weather-related messages trigger webhook notifications. Current Situation We use Microsoft Graph webhook subscriptions on mailbox messages. Weather messages are delivered as standard emails. Subject-based filtering is sufficient for our requirements. We would like to avoid processing every incoming email after receiving notifications. Proposed Approach We are considering stamping weather emails with a custom MAPI extended property when the message is created, for example: Message subject = Weather using a custom single-value extended property. Questions Can Microsoft Graph webhook subscriptions filter notifications based on custom MAPI extended properties? If not directly in the subscription, can $filter be used on message queries against these custom properties after receiving notifications? Has anyone successfully implemented a solution where a custom MAPI property acts as a service tag for weather messages? Are there any recommended alternatives for reducing webhook traffic when only a subset of messages is relevant? Would Outlook categories, message classes, or other Exchange attributes provide a better filtering mechanism than custom MAPI properties? Our goal is to identify weather messages reliably while minimizing unnecessary webhook notifications and mailbox processing. Any guidance, examples, or best practices would be greatly appreciated. Thanks!Proposal: AI‑Powered News Reliability Label for Microsoft Edge
AI‑Powered News Reliability Label for Microsoft Edge Problem: Digital news often contains misleading or exaggerated content, especially in tabloid-style articles that use sensational headlines, omit context, or distort facts to drive clicks. This creates a consumer harm because users waste time on low-quality content, misinformation spreads easily, and trust in online information continues to decline. Digital news is monetised, yet unlike physical products, it has no transparency standards. Proposed Solution: Introduce an optional, user-controlled AI reliability label that appears above online news articles in Microsoft Edge. This label would analyse the article using AI and assign a simple colour-coded reliability score: 🟩 Green — High Reliability 🟨 Yellow — Missing Context 🟧 Orange — Low Reliability 🟥 Red — Click-bait / Misleading Content The label would not block or hide content. It simply provides transparency so users can make informed decisions. Why This Is Safe: • Optional (off by default) • Does not restrict access • Does not censor or demote publishers • AI-generated analysis, not editorial judgement • Equivalent to a “nutrition label” for information Benefits to Users: • Helps avoid misleading content • Builds trust • Saves time • Improves digital literacy • Reduces exposure to sensationalism Benefits to Microsoft Edge: • Differentiates Edge from other browsers • Demonstrates responsible AI leadership • Provides a meaningful use of Copilot • Aligns with Microsoft’s safety and trust principles • Could become an industry standard Technical Feasibility: Microsoft already has the required components: Edge integration, Copilot models, SmartScreen-style UI patterns, and Responsible AI frameworks. Summary: This feature enhances user trust, improves digital literacy, and positions Edge as the first browser to address the growing problem of misleading online content—without restricting access or interfering with press freedom.
Picture-in-Picture seek controls bypass MediaSession ad restrictions on YouTube
In Microsoft Edge, the Picture-in-Picture overlay exposes functional +10s/-10s seek controls during YouTube ad playback. The seek action advances the ad playhead even when YouTube has declared the seekforward action as unavailable via the Media Session API. Repro: InPrivate window, logged out of YouTube Play any video on youtube.com When pre-roll ad starts, click the in-player PiP icon Press +10s seek-forward on the PiP overlay Observed: a non-skippable NPCI ad followed by a Maggi ad were both bypassed in ~10 seconds of wall-clock time. The main <video> element briefly buffers during seek, consistent with HTMLMediaElement.currentTime being mutated directly rather than dispatched through the page's registered MediaSession action handlers. Cross-browser: verified the same flow in Google Chrome on the same Windows install. Seek-forward during ad playback does NOT advance the playhead, confirming YouTube's MediaSession setup is correct and isolating the issue to Edge's PiP implementation. Impact: affects any site using the Media Session API to restrict seek — live streams, DRM-protected content, ad-bound playback. Not YouTube-specific. Environment: Edge version: latest stable channel OS: Windows 11 - Chrome compared: latest stable channel
Add Secure DNS (DNS-over-HTTPS) Support to Edge Mobile
Hello Edge Team, I’ve noticed that while Edge desktop already supports Secure DNS (DNS-over-HTTPS), the mobile version currently lacks this option. Competing browsers like Chrome and Brave allow users to configure Secure DNS directly on mobile, which provides: Improved privacy by preventing ISP-level DNS snooping Consistency across platforms so Edge users enjoy the same protections on desktop and mobile User choice to select trusted DNS providers (Cloudflare, Google, Quad9, etc) Adding Secure DNS support in Edge mobile would strengthen Edge’s privacy posture and align it with modern browser standards. Could the team consider prioritizing this feature in upcoming Insider builds? I believe many users would welcome the option to configure Secure DNS directly within Edge mobile settings. Thank you for your continued work on making Edge a competitive and privacy‑friendly browser.
Propuesta para mejora de Microsoft Edge
Propuesta de mejora para Microsoft Edge: Configuración de carpeta predeterminada por sitio web Asunto: Solicitud de función: Carpeta predeterminada por sitio para cargas y descargas de archivos en Microsoft Edge Estimado equipo de Microsoft Edge: Quisiera proponer una mejora que sería de gran utilidad para profesionales que trabajamos con múltiples plataformas web que requieren la carga y descarga constante de documentos. Actualmente, Edge permite controlar permisos de acceso a archivos por sitio, pero no ofrece la posibilidad de asignar una carpeta predeterminada específica para cada página o dominio. Esta función sería especialmente valiosa en entornos legales, administrativos y gubernamentales, donde distintos portales requieren manejar documentos en rutas separadas para mantener orden, trazabilidad y eficiencia. Beneficios de la función solicitada Reducir tiempos de navegación al seleccionar carpetas en cada carga de archivo. Evitar errores al subir documentos desde carpetas equivocadas. Facilitar flujos de trabajo donde cada plataforma requiere carpetas distintas (por ejemplo: "Acceso" y "Firma"). Mejorar la productividad en sectores que dependen de múltiples portales judiciales, administrativos o corporativos. Propuesta técnica Agregar en la configuración de permisos por sitio una opción como: "Asignar carpeta predeterminada para cargas/descargas en este sitio" Esto permitiría que Edge recuerde automáticamente la carpeta seleccionada cada vez que el sitio solicite subir o guardar un archivo. Estoy seguro de que esta mejora beneficiaría a miles de usuarios que trabajamos diariamente con plataformas que requieren manejo intensivo de documentos. Agradezco su atención y quedo a disposición para aportar más detalles si son necesarios. Atentamente, Víctor Hugo Escobedo Barajas No soy programador, soy abogado y este modificación directo desde configuración por sitio ayudaría bastante a reducir el tiempo de revisión de mis actividades diarias.Next Update for Edge not compatible with my mac
Hi, so I'm so sorry if this isn't the right place or if I'm doing this wrong, but I'm kind of freaking out. So I use Edge on an older mac that cannot be updated as mac no longer supports updates for it. I was previously using Edge Dev and after an update got a message saying that the next update won't be compatible with my mac and I tried not to update but at some point Edge Dev restarted and thus updated and then it wouldn't open on my mac, so I switched back to regular Edge. After the last update on regular Edge, I got the same pop up saying that the next update won't be compatible with my mac and now I'm terrified that when that update comes out at some point Edge will restart and update and then I will lose my ability to use Edge. I love Edge as a browser and have so much stored in it. I have exported my passwords just in case, but am still super scared that I'll lose all the work I've put into Edge and that I'll just lose Edge as it's such a superior browser that I've come to rely on. Does anyone have any suggestions on what I should do? I can't afford to get a new computer right now and as I mentioned my Mac doesn't support updates. Any help would be unbelievably appreciated. Thanks in advance.
Extensions
I haven't really been paying attention to what does or does not work in Edge Dev and Canary recently. But today I had issues again with Canary. I completely cleaned out all the stored data and reinstalled it. I noticed that all the extensions disappeared. I went looking for them to replace the few I actually used and got a message telling me that they are no longer available for this version of Edge. I get the same message on Dev. But production Edge allows them to be turned on and added to. Has anyone else run into this or am I missing something in the setting that change and I have totally overlooked.
