Edge 79 and Chrome do not support this registry key. Edge 18 and Internet Explorer allow an App Protocol handler to opt-out of warning the user on open using the WarnOnOpen registry key.This API is not available in Edge 79 or Chrome. Edge 18 and Internet Explorer offer a msLaunchUri API for launching and detecting App Protocols.In Chrome/Edge79, the navigation attempt is silently ignored. In Edge18 and Internet Explorer, attempting to navigate to an App Protocol with no handler installed shows a prompt to visit the Microsoft Store to find a handler.For security reasons, Edge79 and Chrome block navigation to file:// URLs from non-file URLs, although Edge 95+ has a policy to somewhat relax that. ![]() Note: I’ve previously blogged about interop issues between Edge18 and Chrome. We expect there will be some behavioral deltas between Edge79+ and its Chrome-peer versions, so I’ll note those here too. ![]() When comparing Edge and Chrome behavior, be sure to compare against the corresponding Chrome Stable, Beta, Dev and Canary channels Edge 80 vs Chrome 80, etc. In general, Edge79+ will behave very similarly to Chrome. Compatibility DeltasĪs our new Edge Insider builds roll out to the public, we’re starting to triage reports of compatibility issues where Edge79+ (the new Chromium-based Edge, aka Anaheim) behaves differently than the old Edge (Edge18, aka Spartan, aka Edge Legacy) and/or Google Chrome. Note: I expect to update this post over time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |