• webwitnl


    I submitted a very specific bug report which causes browsers to crash due to Mollie firing itself like 7-10 times, loading and firing over 7MB of javascript and stuff. They need to throttle the change event on checkout like other checkout elements/plugins. Silence for almost a month now. These are amateurs. If they would have been pros, they would immediately act on this bad implementation. Instead, seems no one cares at Mollie.

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support Syde Niklas


    Hi there,

    Thank you for your feedback and for providing a detailed bug report. We acknowledge your concerns about the performance issue you’ve encountered with the Mollie Components.

    We want to assure you that the issue is under active investigation. Issues are prioritized based on how common they are and their impact, and while we haven’t been able to reproduce this particular issue yet, the development team is still investigating.

    We appreciate your patience and understanding while we continue our efforts to diagnose and address the issue you reported. Once we have an update or need additional information, the team will get back to you.

    Kind regards,

    Thread Starter webwitnl


    Hi, I “solved” this with help of Mollie support, although the core problem is still there. What made the problem go away was to deactivate the “Mollie components” in the settings for credit cards payments.

    With this deactivated, when someone chooses to pay by creditcard, the details are entered after order confirmation on the Mollie pages. When activated, you enter it on the shop’s order confirmation page.

    There, this component is an iframe which loads lots of javascript and css, and reloads at every form change event (which can be a lot). This caused the crashes.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Crashes browser, Mollie does nothing’ is closed to new replies.