--js-flags=--noexpose_wasm launch flag causes STATUS_BREAKPOINT
Version 135.0.3179.73 (Official build) (64-bit), Windows 11 Education, also occurs on Windows 10 Education and Windows 10 Pro, been testing this since probably version 129 of Edge. --js-flags=--noexpose_wasm as a launch flag causes STATUS_BREAKPOINT, this is regardless of default configuration and with or without extensions. WASM can be used to discover privileged information about a machine, and this seems to be working in the past according to some users online, but no longer does now. Please can someone advise?
Teams App: "Always Open in Desktop App" does not work on Search results file list
I have my settings so that files open in native app when I open from Teams app and it works fine within document folders within channels. When I use the search bar (and then select the Files option) to find a file and then click on the link, or on the Open File button it always opens in browser and not in native app. Seems pretty odd defect tbh. How do I fix this please? thanks
Teams "Mark as Read" on Android app not applying on Desktop teams.
I'm reporting this as a bug. (Yes, this is probably not the appropriate place for this, but I couldn't find a better one). In the Android app (not sure if applies to iOS), when you mark a chat as read by long pressing and tapping on the "Mark as read" item, this does not cause the chat to show up as read on the Windows Desktop Teams app. I'm guessing it doesn't mark it read on the server. Note that if you open the chat and read it on the Android app, it does appear read as expected on the Desktop app. Also it does work the other way - Marking as read in the Desktop version does cause the Android version to appear as read.
