We managed to reproduce this bug but it looks like we will need to update the component code in order to fix the issue. We are not yet able to say when exactly a new version containing this fix will be released.

As a workaround for now, please try to add this code to the component/components in which you use the <mdb-multi-range>. For example in the ngOnInit hook:

  ngOnInit(): void {
    for (const type of ['TouchEvent']) {
      if (typeof window[type] === 'undefined') {
        window[type] = function () {};
      }
    }
  }