YassielO.21521 (Customer) asked a question.
Custom link added in the "afterTransform" not working
Hello, we are using OKTA OIE 3rd generation widget, and as part of the customizations we are doing for the sign-in widget, we are experiencing some issues.
As you can see, our link is properly displayed in the UI, and if we mouse over it, it shows that it has the "mailto" in the href. The strange part is that it is not doing anything when we click on it. Could the widget be capturing the click event somehow and stopping the propagation?
Please find below the code we have in the "afterTransform" hook:
Since you say you can see the proper mailto address when you hover over the link, have you ruled out this perhaps being a browser issue rather than an Okta issue? For example: https://stackoverflow.com/questions/17517600/mailto-links-do-nothing-in-chrome-but-work-in-firefox
Hi @MatthewH.10249 (State of Iowa), thanks for your reply. I don't think that's it because I did try in other browsers. Also, I did a test like this:
The "Help" link works as expected but the "contact us" doesn't
Thanks!
@MatthewH.10249 (State of Iowa) this is the generated code for both links if that helps:
I'm not seeing anything with that link that looks incorrect. Are other mailto links from other websites working on your PC or have you tried accessing from a different PC? If no mailto links are working the following explains how a default mail client needs to be set.
https://stackoverflow.com/questions/34129707/href-mailto-is-not-working-on-any-of-the-browsers
If other mailto links work on your PC and your Okta one does not work on other PCs then the only other thing I can think of would be to look for errors using developer tool in your browser (F12). Look at the output of the developers tools before and after you try pressing the link.
Hi @MatthewH.10249 (State of Iowa),
Thanks for your reply. As I mentioned in my previous comment, the first link in the example above works, but the second one does not. This leads me to believe that the issue is related to the widget itself, rather than a browser problem, as other links are working fine.