Crash when submitting web page input fields with soft keyboard Enter
### Summary Microsoft Edge Canary for Android crashes when submitting web page input fields using the Android soft keyboard Enter key. GitHub search is one stable reproduction case, but this is not GitHub-specific. I have also reproduced similar crashes on other websites with text input/search fields. ### Environment - App: Microsoft Edge Canary for Android - Package: `com.microsoft.emmx.canary` - Version: `152.0.4142.0` - Version code: `414200023` - Device: vivo V2417A - Android SDK: 36 - ABI: arm64-v8a ### Reproduction case 1. Open Microsoft Edge Canary on Android. 2. Navigate to `https://github.com/`. 3. Tap the GitHub search box. 4. Type any text. 5. Press Enter on the Android soft keyboard. ### Expected behavior The input/search action should be submitted normally. ### Actual behavior Edge Canary crashes immediately after pressing Enter. ### Scope This does not appear to be specific to GitHub. The same type of crash can also be triggered on other websites when submitting text input/search fields using the Android soft keyboard Enter key. GitHub is used here as a minimal stable repro because it is easy to test. ### Crash information Exception: ```text java.lang.IndexOutOfBoundsException: Index 24 out of bounds for length 0 ``` Relevant stack trace: ```text java.util.ArrayList.get(ArrayList.java:434) android.view.ViewGroup.getAndVerifyPreorderedView(ViewGroup.java:3873) android.view.ViewGroup.gatherTransparentRegion(ViewGroup.java:7438) android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:5207) android.view.Choreographer.doFrame(...) ``` ### Notes - Reproduced directly on the Android phone. - Trigger appears related to submitting web page input/search fields via the Android soft keyboard Enter key.
[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!
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 channelEdge Dev on Windows - Tab sync not working
Just wondering if anyone else is seeing a bug where on Windows and Edge Dev (latest version), tab sync just says "No tabs from other devices". But if you go to Edge Stable, it does show open tabs. It also shows my recent tabs with Edge Dev on Android, so I know the sync is working, just the desktop client is not showing them. I've sent feedback for this issue but since sync is still working correctly, I am wondering if this is a UI bug.Critical Edge Sync issue after Win11Pro reinstall – incomplete rehydration
A - ENGLISH VERSION Critical Edge Sync issue after Windows 11 Pro reinstall – incomplete rehydration, Device Info = 5, modules stuck Hello, I am experiencing a major issue with Microsoft Edge synchronization after a full reinstall of Windows 11 Pro. Despite multiple reinstalls, several days of waiting, and all possible local troubleshooting steps, Edge Sync remains incomplete, and none of my historical data is rehydrated. Below is the full context, timeline, symptoms, technical observations, and questions. 1) Full chronological context 1.1 – Full PC reset Clean Windows 11 Pro reinstall Sign‑in with Microsoft personal account Windows Insider Program activated (Beta channel) 1.2 – Edge Beta installed automatically Edge Beta was installed automatically without warning. I suspected it might be the cause of the incomplete sync. 1.3 – Leaving the Insider Program I left Insider only to try restoring full Edge synchronization. 1.4 – New Windows 11 Pro 25H2v2 reinstall Clean install Edge Stable installed Sync enabled Several days of waiting 1.5 – Result: sync still incomplete Even on Edge Stable, historical data never returns. 2) Symptoms 2.1 – Missing data No previous tab groups restored Incomplete history “Other devices” sessions missing Passwords visible in settings but not rehydrated No data from my previous Windows 11 PC 2.2 – Sync modules stuck In edge://sync-internals: Saved Tab Group: frozen for days Passwords: “Running” but no data rehydrated Sessions: incomplete Typed URLs / History: partial 2.3 – Device Info = 5 The cloud still lists 5 devices, including my previous Windows 11 installation. This indicates that historical data should be available. 2.4 – Last Synced active Sync is active, but missing data is never returned. 3) Technical diagnosis Everything points to a “consistent but incomplete” cloud profile state: Client sync works Server reports sync as healthy Historical data is never rehydrated Critical modules remain stuck Issue reproduces across multiple devices (Win10, Win11) This suggests a server‑side Edge Sync profile corruption, or a metadata divergence after: Insider → Stable channel change Windows reinstall Local profile deletion Edge Beta auto‑installation Microsoft account reconnection 4) Key question: Is Edge Beta limited in synchronization? I would like an official clarification: → Does Edge Beta restrict any sync modules? → Are Saved Tab Group, Sessions, or Passwords limited in Edge Beta? → Are there backend differences between Edge Stable and Edge Beta? If Edge Beta is not the cause, I will gladly re‑enable my Insider profile. I left Insider only to attempt restoring full sync. 5) Request I kindly request: → A backend analysis of my Edge Sync profile, to check: metadata integrity module states device list consistency possible corruption ability to rehydrate historical data I can provide: sync‑internals screenshots logs additional details multi‑device testing Thank you very much for your help. B - VERSION FRANÇAISE Problème critique de synchronisation Edge après réinstallation Windows 11 Pro – réhydratation incomplète, Device Info = 5, modules bloqués Bonjour, Je rencontre un problème majeur avec la synchronisation Microsoft Edge, apparu après une réinitialisation complète de mon PC Windows 11 Pro. Malgré plusieurs réinstallations, plusieurs jours d’attente, et toutes les procédures locales possibles, la synchronisation reste incomplète, et mes données antérieures ne sont jamais réhydratées. Je détaille ci‑dessous l’ensemble du contexte, les étapes, les symptômes, les observations techniques et les questions. 1) Contexte chronologique complet 1.1 – Réinitialisation complète du PC Réinstallation Windows 11 Pro “vierge” Connexion au compte Microsoft personnel Activation du programme Windows Insider (canal Bêta) 1.2 – Edge Bêta installé automatiquement Sans avertissement ni information, Edge Bêta a été installé automatiquement sur mon système Insider. Pensant que Edge Bêta pouvait être la cause d’une synchronisation incomplète, j’ai tenté de revenir à Edge Stable. 1.3 – Sortie du programme Insider J’ai quitté le programme Insider uniquement pour tenter de retrouver une synchronisation Edge stable et complète. 1.4 – Nouvelle réinstallation Windows 11 Pro 25H2v2 Installation propre Edge Stable installé automatiquement Synchronisation activée Plusieurs jours d’attente pour réhydratation 1.5 – Résultat : synchronisation toujours incomplète Même après retour à Edge Stable, les données antérieures ne reviennent pas. 2) Symptômes observés 2.1 – Données manquantes Aucun groupe d’onglets antérieur n’est restauré Historique incomplet Sessions “Autres appareils” très partielles Mots de passe visibles dans les paramètres mais non réhydratés dans l’interface Données provenant de mon ancien PC Windows 11 absentes 2.2 – Modules Edge Sync bloqués Dans edge://sync-internals : Saved Tab Group : valeur figée depuis plusieurs jours Passwords : module “Running” mais aucune donnée réhydratée Sessions : incomplètes Typed URLs / History : partiels 2.3 – Device Info = 5 Le cloud conserve encore les identifiants de 5 appareils : PC Windows 10 Smartphone PC Windows 11 actuel PC Windows 11 avant réinstallation PC Windows 11 Insider (Edge Bêta) Cela prouve que les données de l’ancien appareil devraient être disponibles, mais ne sont pas renvoyées au client. 2.4 – Last Synced actif La synchronisation est active, mais ne renvoie pas les données manquantes. 3) Diagnostic technique Tout indique un état “cohérent mais incomplet” du profil cloud Edge : Le client synchronise correctement Le serveur considère la synchronisation comme valide Mais les données historiques ne sont jamais renvoyées Les modules critiques (Saved Tab Group, Passwords, Sessions) restent bloqués Le problème est identique sur plusieurs appareils (Win10, Win11) Cela suggère une corruption du profil Edge Sync côté serveur, ou une divergence entre métadonnées locales et cloud après : changement de canal (Insider → Stable) réinstallation Windows suppression du profil local Edge Bêta imposé réactivation du compte Microsoft 4) Question cruciale : Edge Bêta est‑il bridé dans la synchronisation ? Je souhaite obtenir une réponse officielle : → Edge Bêta limite‑t‑il certaines fonctions de synchronisation ? → Certains modules (Saved Tab Group, Sessions, Passwords) sont‑ils restreints dans Edge Bêta ? → Existe‑t‑il des différences de backend entre Edge Stable et Edge Bêta ? Si Edge Bêta n’est pas en cause, je serai heureux de réactiver mon profil Insider. J’ai quitté Insider uniquement dans l’espoir de retrouver une synchronisation complète. 5) Demande Je sollicite : → Une analyse backend de mon profil de synchronisation Edge pour vérifier : l’intégrité des métadonnées l’état des modules la cohérence des appareils la présence ou non d’une corruption la possibilité de réhydrater les données historiques Je suis prêt à fournir : captures edge://sync-internals journaux détails supplémentaires tests sur plusieurs appareils Merci d’avance pour votre aide.
