sbernado

Awesome. Appreciate your response. Thank you and have a great day!

Hello! Thank you for your work on this! Much appreciated.

I am using version 2.1 and iThemes security is still flagging the plugin with a vulnerability.

WordPress Side Cart Woocommerce (Ajax) plugin <= 2.1 – Cross-Site Request Forgery (CSRF) vulnerability

Thanks again!- scott

“However, So far I use Google custom search, it’s able to pick up the MPG pages on the site.”

Thanks for the tip!

Thank you for your reply, Oleksandr!

At least now I know this isn’t possible by default ??

Thanks again. – scott

Hi again ?? I checked out the link, but I am not sure how this works. Does that code go in the functions.php file? How do I add a search field to my pages? Thank you so much for your help. Thank you.

Thank you, Oleksandr. Appreciate the link and help.

Hi @aaronrobb,

Any luck on this yet?
Just had a client inquire about something similar today.
Wondering if you were successful in your search ??

Thank you. – scott

Hi Curtis.

I agree that Exit Notifier is doing things properly (inspecting anchor tags), and that Divi is causing the issue, but the issue still persists within one of the most popular themes ??

Thanks anyway.

I am adding it through Appearance >> Menus >> and then adding the “noExitNotifier” to the class field within a menu item (view the Screen Options at top of the page to ensure it is checked off or you will not see class as an option).

Does that answer your question?

Hi Curtis,
Thank you for your quick reply.
I actually came up with a jQuery workaround, but I think a solution within the plugin would be cleaner.
Here is the HTML code and a workaround:
<li class="orange fordesktop noExitNotifier menu-item menu-item-type-custom menu-item-object-custom menu-item-234580"><a href="https://www.domain.com/123/">Online Banking</a></li>
In the above code, the “li” class “noExitNotifier” is ignored.
Here is my working jQuery solution:
$(".orange a").attr("class","noExitNotifier");
Hope that helps ?? Thanks again. – scott

• This reply was modified 4 years, 3 months ago by sbernado.

That was quick ?? I just tested 1.8.2 and it is working perfectly for me. Nicely done! Thank you so much, Curtis! – scott

Happy to help. It’s the least I can do ??

That sounds great! Thanks again, Curtis.

Hi Curtis,

I apologize, but I am working on another project at the moment, however, I tested using your own page as I noted above, so the issue would not be my js version ??

I do not expect the focus to leave the popup once the popup is displayed. A user should be able to hit OK, Cancel or Esc to exit. That is all. Tabbing through the menu and address bar only adds confusion, and is not compliant, from my understanding.

Check out this link (https://www.w3.org/TR/wai-aria-practices-1.1/examples/dialog-modal/dialog.html) and scroll to the light blue box with the heading Keyboard Support. This explains compliant behavior.

Hope that helps, Curtis! Thanks again for you work on this. It is appreciated and I admire your intelligence and determination to get this working ?? – scott

Hi Curtis – I have the same issues as TinCabinStudios noted. On your test page, if I hit tab multiple times, the focus gets lost and I cannot exit the popup. I think in the beta you let us try a couple of weeks ago, the focus would toggle back and forth between the OK and Cancel buttons infinitely, with each press of the tab key, and the escape key would properly exit the popup.

To reproduce my results, go to: https://cvstech.com/exitnotifier/ >> Click external link >> Hit tab key 2 or more times >> hit escape key (popup does not close) >> Or press enter and nothing happens

HTH ??

• This reply was modified 4 years, 6 months ago by sbernado.

Awesome! I will let you know as soon as I am able to test it out. Thank you for the heads up and all your hard work porting this over. Much appreciated!