Improve Password Manager granularity for paths and fix OTP misidentification

علي الخضر 0 نقاط السُمعة
2026-04-29T12:39:49.7366667+00:00

I switched from Chrome to Edge, and I'm very impressed with the performance. However, as a developer, I've noticed two key issues with the built-in password manager compared to Chrome:

  1. Lack of password path segregation:

Edge treats all accounts within the same domain (or localhost) as a single entry. For example, it doesn't differentiate between xx.com/admin and xx.com/user. This is a major obstacle when developing locally on http://localhost/, as Edge suggests the same credentials for every project. I suggest implementing path-based password management, similar to Chrome's behavior.

  1. Incorrect One-Time Password (OTP) recognition (incorrect "Update Password" prompt):

Edge frequently prompts for "Update Password" when entering a two-factor authentication/OTP code in a numeric field. The algorithms for identifying password fields seem overly stringent, leading to confusion and incorrect password substitutions.

Desired behavior:

The password manager should recognize specific paths when suggesting credentials.

Improved detection of one-time verification code/password fields to prevent incorrect password update prompts.

Is there a way to avoid these issues?

Microsoft Edge | غير ذلك | Windows 11
0 تعليقات

إجابة واحدة

فرز حسب: الأقدم
الأكثر فائدة الأحدث الأقدم
  1. Lychee-Ng 28,915 نقاط السُمعة فريق عمل موظفين Microsoft الخارجيين المشرف
    2026-04-30T07:59:58.1066667+00:00

    This is posted in the Arabic section, but since you are using English, the content below has been written in this language.

    Hi علي الخضر,

    Thank you for taking the time to share this. Your feedback on these behaviors is valid, and shared by other developers. Edge’s password manager is scoped to sites, not URL paths, to keep credential handling consistent for most websites. However, this design can be limiting for localhost‑based development workflows where multiple apps share the same domain.

    At the moment, there has yet a way to avoid either behavior in Microsoft Edge, but I believe it's worth looking forward to the next updates. For now, here's a few workarounds you can try out to see if it improves the experience:

    • Different ports instead of paths (e.g. localhost:3000, localhost:4200)
    • Use separate browser profiles and auto-switch feature:
      • Open Edge > Settings > Profiles > Profile preferences
      • Turn ON (optional) Automatic profile switching options
    • Look for a third‑party password managers with path rules.

    It's also worth noting that the Microsoft Q&A is just a user-to-user support forum, and while developers may come by from time to time, this is not the best place to do so if you want to give them feedback. To escalate properly:

    • Use the browser built-in channel:
      • Click three-dot next to profile > Help and feedback > Send feedback
      • Or you can press Alt + Shift + I
    • Another official Microsoft's feedback channel is Feedback Hub (press Win + F)

    Your expectations are completely reasonable. However, if the feedback is sent to the wrong place, it may not be noticed or acted upon. Submitting it through the official feedback channel is the most effective way to ensure it gets proper attention.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    هل كانت هذه الإجابة مفيدة؟

    شخص واحد وجد هذه الإجابة مفيدة.

إجابتك

يمكن وضع علامة على الأجوبة 'كمقبولة' من قبل كاتب السؤال و'مستحسنة' من قبل المشرفين، مما يساعد المستخدمين على معرفة الإجابة التي حلت مشكلة الكاتب.