Urgent: bug in released version of Edge, workaround in extension is waiting to get published

[merijndejonge]

Hello,
There is a bug in Chromium, which was reported https://issues.chromium.org/issues/500975618?pli=1.
But with the latest version of Edge the bug is now in production.
The effect of the bug is that people cannot signin in our password manager. The issue also seems to affect other password managers as well.

Last week, we already submitted a workaround for it, but it is still under review. With the recent release of the latest version of Edge, our customers start complaining that the cannot sign in any more.

Is het possible to give high prio to the review of our browser extension, such that people don't get stuck because of this bug?

The extension id is: mlafkblkhbjggodkbcngbdblcmpmjpog

Thanks!

[Rahul-Bauri]

Hi @merijndejonge thanks for reporting the bug. I’ll check with the engineering team to investigate this further and will update here once I receive any updates from them.

[merijndejonge]

Thanks @Rahul-Bauri for picking it up.
Please, know that a growing number of customers is complaining and this number is growing fast. Once the latest version of our extension, which contains a workaround for the bug in Chromium, passed the review process, our customers can continue their work.
So, can I ask again to help us by completing the review process right now?

Thx!

[here-nerd]

@Rahul-Bauri the bug is inherited from Chromium. Edge has introduced it by adopting Chromium 147 even after it was reported on the Chromium bug tracker. If you see https://issues.chromium.org/issues/500975618?pli=1, you will understand how big the issue is, 1Password, Keeper, PassBolt, potentially many more are impacted by it.

It is very proactive of a web extension to have a hotfix to work around it before you guys fixing it. So just a little help from your review team to approve @merijndejonge 's web extension promptly would be really appreciated.

[Rahul-Bauri]

Hi @merijndejonge I can see that your latest submission was done on 4/11/2026, 12:05:39 AM, please note that it typically takes 5-7 business days to complete the review process, once the review is completed successfully your updated extension will be live on the Edge store.

The team is already investigating the issue, and I will update here once I have any updates from them.

[merijndejonge]

Dear @Rahul-Bauri,
As @here-nerd indicated, Microsoft released a new version of Edge while it was already known that it contained a bug. This is a very unfortunate and urgent situation. Last week we already developed a workaround and published it last Friday (for Chrome and Edge). In Chrome it was released on the same day, for Edge we're still waiting.

We get a couple of hundred phone calls per day from users and customers complaining about the issue. This is bad for our reputation, but even more for our users.
I kindly, but urgently ask you to give top-prio to review our browser extension, which is in your store for many years now, and get it published today.

BTW for releasing our browser extension with the workaround, there is no need to investigate the issue. Just push it through the review process with top-prio.

Can I count on you?

Best regards,
Merijn de Jonge
CEO MindYourPass

[here-nerd]

Hi @Rahul-Bauri, standard timelines work for regular feature updates and minor fixes, but not for critical fixes responding to platform-level issues beyond the developers' control. If your review process cannot accommodate urgent, platform-triggered issues, this significantly undermines the platform's viability for developers who rely on timely support -- what do you need to investigate anyway? They just ask you to speedy approve their hotfix.

[merijndejonge]

It's published. Thanks to all of you!

[Rahul-Bauri]

Going to close this issue here, feel free to open a new bug if you face any issues in the future, Thanks.