We have a custom policy with Custom HTML that we developed for our Sign-In page based off of Azure AD B2C. Most of the time it works well, but every so often the page will be completely unresponsive - the sign in button doesn't work, sign up doesn't work, etc. I've inspected the Network tab when it's come up and nothing happens there - there's no requests to the backend server, it's like the buttons just aren't being connected.
We can solve the problem by refreshing the page, and usually it's fine afterwards. But we're hoping that there might be something we can do to fix the problem so that it won't happen at all.
There doesn't seem to be any consistent way of reproducing it, but we have noticed that it happens more often if we:
- open a private browser window (Edge InPrivate, Chrome Incognito, etc)
- for username instead of typing it in manually, select it from the dropdown (if you've signed in before with that browser it may be available -- see screenshot below)
- enter Password manually
- Click login button
I've been taking a look but it looks like this is something deeper in B2C, so I don't think there's anything I can do with it from the policy side. We do have some Custom JS integrated into the web page, but it's nothing that would affect any of the buttons (all we're doing is adding some classes to some of the page elements).
Let me know if there's anything else I can provide to help figure out what's going on. Has this happened before / is there anything I can do to fix the issue? Thanks!