Thanks Dan,
I can see that you have suggested using the “signin ready” even function of yours in order to have it execute a specific command that would remove, not hide the button.
It is important for me to make a few observations and corrections here.
-
In my report I pointed out that the mentioned “signin ready” function does not get triggered. However, I now noticed that I had made a mistake when I was quoting this function.
In my post I may have perhaps misled you to believe that we did not use correctly your function as it should be closed correctly with }) and not }} as I wrongly posted in my initial message. Please accept my apologies for this. Adding any code to this function did not work for us. We shall re-try again and see if we have only the code you provided for the function, in case that helps. -
How can you guarantee that your solution will not be removing the button that is needed for an application that would need it to stay? Your solution only removes an item based on its ID being specifically named “1-submit”. Perhaps you know something that we are not aware of.
-
If removing the submit button is an acceptable and recommended option for auth0 then that is fine with us, we do not insist on specifically hiding the submit button when it is not expected to be present on a login page where there is nothing to be submitted. Ideally, auth0 should detect such cases and adjust what buttons are sensible to be presented without the need for a fix via code customisation or if there were more config settings available. I assume our setup is not a common use case scenario and may require some investigation.
If I do not post shortly confirming that the issue is solved, please consider it as still standing.
Thank you for your time