[TASK] Remove the custom close event because the native HTML dialog element has its own close event

Author: deoostfrees

README.md

@@ -300,7 +300,7 @@ The following events are available:
 | `close` | Triggered after Parvus has been closed |
 | `destroy` | Triggered after Parvus has been destroyed |
 
-Except for the `destroy` event, you can access the current source element using the `event.detail.source` property.
+Except for the `close` and `destroy` events, you can access the current source element using the `event.detail.source` property.
 
 ```js
 prvs.on('open', function (event) {

dist/js/parvus.esm.js

@@ -523,13 +523,6 @@ function Parvus(userOptions) {
     IMAGE.addEventListener('transitionend', transitionendHandler, {
       once: true
     });
-
-    // Create and dispatch a new event
-    fire('close', {
-      detail: {
-        source: GROUPS[activeGroup].triggerElements[currentIndex]
-      }
-    });
   };
 
   /**

dist/js/parvus.esm.min.js

@@ -529,13 +529,6 @@
       IMAGE.addEventListener('transitionend', transitionendHandler, {
         once: true
       });
-
-      // Create and dispatch a new event
-      fire('close', {
-        detail: {
-          source: GROUPS[activeGroup].triggerElements[currentIndex]
-        }
-      });
     };
 
     /**

dist/js/parvus.js

@@ -519,13 +519,6 @@ export default function Parvus (userOptions) {
     }
 
     IMAGE.addEventListener('transitionend', transitionendHandler, { once: true })
-
-    // Create and dispatch a new event
-    fire('close', {
-      detail: {
-        source: GROUPS[activeGroup].triggerElements[currentIndex]
-      }
-    })
   }
 
   /**