[Milestone/Release Version 1.1.0] New Features & Request

.circleci/config.yml

@@ -0,0 +1,19 @@
+version: 2.1
+
+orbs:
+  node: circleci/[email protected]
+jobs:
+  build_and_test:
+    docker:
+      - image: circleci/node:latest
+    steps:
+      - checkout
+      - node/install-packages:
+          app-dir: ~/project/NPM (NodeJS)
+      - run:
+          name: Run linters and tests
+          command: cd "NPM (NodeJS)" && npm run test-verbose
+workflows:
+  build_and_test:
+    jobs:
+      - build_and_test

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,42 @@
+---
+name: Bug report
+about: Create a report to express frustrations & improve this project
+title: "[Bug] Bug_(&Suggested_Bug-fix,_if_applicable)_Request"
+labels: bug, help wanted
+assignees: ''
+
+---
+
+**Describe the bug**
+A clear and concise description of what the bug is.
+
+**To Reproduce**
+Steps to reproduce the behavior:
+1. Go to '...'
+2. Click on '....'
+3. Scroll down to '....'
+4. See error
+
+**Expected behavior**
+A description (obvious ones too, these are appreciated!) of what you expected to happen.
+
+**Screenshots**
+Any bug with screenshots will be prioritised. Please include them to help explain your problem.
+
+Most desktop and mobile OS have these features, but if you are willing to contribute and are not sure how, state so in this section and I will try to guide you through how to take screenshots.
+
+**Operating Systems Affected**
+
+***Desktop (please complete the following information):***
+ - OS: [e.g. iOS]
+ - Browser [e.g. chrome, safari]
+ - Version [e.g. 22]
+
+***Smartphone (please complete the following information):***
+ - Device: [e.g. iPhone6]
+ - OS: [e.g. iOS8.1]
+ - Browser [e.g. stock browser, safari]
+ - Version [e.g. 22]
+
+**Additional context**
+Add any other context about the problem here. (Optional, there often won't be such information.)

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: "[Feature Request] REQUEST_HERE"
+labels: enhancement
+assignees: ''
+
+---
+
+**Is your feature request related to a problem? Please describe.**
+A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
+
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.
+
+**Additional context**
+Add any other context in text about the feature request here.
+
+**Screenshots**
+Add any screenshots (optional only in exceptionally minor) requests, depicting what you want changed (or added/deleted) with the assistance of text-boxes, arrows, and other such markup tools.
+
+Most paint/screenshot/[GIMP](https://www.gimp.org)/image editing programs have these features, but if you need something to get you started I've had good experiences with [PaintZ](https://paintz.app) on the web and [Skitch](https://evernote.com/products/skitch) for Desktop.

.gitignore

@@ -0,0 +1,3 @@
+.DS_STORE
+.DS_Store
+NPM (NodeJS)/node_modules/

CONTRIBUTORS.md

@@ -0,0 +1,54 @@
+# Contributors
+
+## Technical
+In addition to this project there is a [website](https://perimeterx.github.io/map-events-website/) that should show the events map of every (OS + Browser) combination that ever existed.
+
+In reality however, it shows most of the existing combinations, but not all of them.
+
+The original maps were extracted using every existing combination in [browserstack](https://browserstack.com), and some more updates were added from manual testing on relatively new browser versions about a year later, but even in browserstack many automatic combinations have failed + there are missing versions in between the two runs + for future versions not yet maintained.
+
+Also, the working extraction script is not automatic and does not run every time there's a new Browser/OS.
+
+Contributing to the [JSON](https://github.com/perimeterx/map-events-website/blob/master/data.json) could help a lot with maintaining the map and keeping it as updated and as accurate as possible.
+
+## Translations, Formatting, Documentation(, and more!)
+
+Other non-technical contributions are encouraged!
+
+In addition to technical contributions (such as the above),
+
+- contributions to the translations, 
+- useful formatting changes, 
+- documentation for the purpose of the site, on the site (and probably other documentation),
+- and of course, additions to the [data](https://github.com/alexwiegmanpx/map-events-website/blob/master/data.json) from your browser on your OS
+of the [webpage](https://github.com/alexwiegmanpx/map-events-website) are all encouraged.
+
+Please clone and make PRs to either [my version of the repository](https://github.com/alexwiegmanpx/map-events-website) or the [official PX version](https://github.com/PerimeterX/map-events-website).
+
+## List of Contributors
+
+Original Author: 
+
+- [Gal Weizman](https://github.com/weizman) | [PerimeterX](https://github.com/galpx)
+
+Currently Maintaining Contributor: 
+
+- [Alex T.W.](https://github.com/madicetea) | [PerimeterX](https://github.com/alexwiegmanpx)
+
+Internal Contributors:
+
+(Your name here 🙂)
+
+Community Contributors:
+
+- [Vasilii Kovalev](https://github.com/vasilii-kovalev) for a good refernece in his [config.yml](https://github.com/vasilii-kovalev/games_world/blob/f910483ccd33a6cf58765f70ee6f6823239011e1/.circleci/config.yml) for how to CircleCI test correctly.
+
+(Your name here 🙂)
+
+Everyone's work is highly appreciated. Thank you!
+
+## Disclaimers
+
+While the work is done on behalf of PerimeterX, any tools, processes, hosting providers, programming languages, or etc. used are representative of the authors and contributors of the open source community + not necessarily representative of the official views of PerimeterX. No part of this repository, code, associated websites, or cloned versions of any of thereof be interpreted to favor, endorse, or otherwise bias (positive or negative) towards any person, organisation, company, or other entity.
+
+If there is any questions or suggestions about this, we encourage the community at wide to open an issue for consideration upstream to the official PerimeterX version of the repository.

LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2019 PerimeterX
+Copyright (c) 2019 - PerimeterX
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+SOFTWARE.

NPM (NodeJS)/README.md

@@ -0,0 +1,117 @@
+# NodeJS Guidance
+
+This directory is for those who will use NodeJS to run this.
+
+Personally, I got as far as correctly getting the installation done, but the usage section neither worked in terminal (UNIX/Mac) nor in a VS Code-Started Debug Session within Brave (Chromium).
+
+So, I made a manual script instead.
+
+## installation
+
+`npm install px-map-events --save`
+
+## usage
+
+```javascript
+const getEventsMap = require('map-events');
+
+const EventsMap = getEventsMap();
+```
+
+## output
+
+a map of all events in the browser in the following format:
+
+```javascript
+{
+    'OBJECT': [
+        'EVENT1',
+        'EVENT2',
+        'EVENT3'
+    ]
+}
+```
+
+# example
+
+```javascript
+const getEventsMap = require('map-events');
+
+const webSocketEventsMap = getEventsMap('WebSocket');
+
+(webSocketEventsMap == {
+  "WebSocket": [
+    "open",
+    "error",
+    "close",
+    "message"
+  ] // results in true
+});
+```
+
+here's an example of how to register with your own listener to every event that exists on `window`!
+
+```javascript
+
+const windowEventsMap = getEventsMap('window')['window'];
+
+for (let i = 0; i < windowEventsMap.length; i++) {
+  const event = windowEventsMap[i];
+  window[event] = (event) => { console.log(event) });
+}
+```
+
+## options
+
+1. `filter` (first optional argument)
+
+allows you to pass a string that must exist within the object in order for it to make it to the final result map:
+
+```javascript
+const getEventsMap = require('map-events');
+
+const EventsMap = getEventsMap('*'); // will return a non-filtered map
+const EventsMap = getEventsMap('HTML'); // will return a map that only contains objects that contain the string 'HTML' (such as 'HTMLBodyElement')
+const EventsMap = getEventsMap('Doc'); // will return a map that only contains objects that contain the string 'Doc' (such as 'Document')
+```
+
+default value: `'*'`
+
+2. `hasOwnProperty` (second optional argument)
+
+allows you to pass a boolean that indicates whether iterated object must has iterated property as its own property or not:
+
+```javascript
+const getEventsMap = require('map-events');
+
+const EventsMap = getEventsMap('*', true); // will return a map with objects and  events properties that are the object's own properties
+const EventsMap = getEventsMap('*', false); // will return a map with objects and  events properties - whether the properties are the object's own properties or not
+```
+
+default value: `true`
+
+3. `noEmptyArrays` (third optional argument)
+
+allows you to pass a boolean that indicates whether final result object should contain objects that have zero events or not:
+
+```javascript
+const getEventsMap = require('map-events');
+
+const EventsMap = getEventsMap('*', true, true); // will return a map with objects and events properties only if the object even has any events
+const EventsMap = getEventsMap('*', true, false); // will return a map with objects and events properties whether the object has any events or not
+```
+
+default value: `false`
+
+4. `debug` (fourth optional argument)
+
+allows you to pass a boolean that indicates whether to run module in debug mode or not. debug mode just logs errors in case any are thrown:
+
+```javascript
+const getEventsMap = require('map-events');
+
+const EventsMap = getEventsMap('*', true, true, true); // will run in debug mode
+const EventsMap = getEventsMap('*', true, false, false); // will not run in debug mode
+```
+
+default value: `false`

NPM (NodeJS)/index.js

@@ -0,0 +1,78 @@
+// Title: Output Browser Events from all Prototype Objects for Every Browser
+// Purpose: Snippet to insert into Browser Console to output all events of all prototypes for every browser
+// Authors: Alexander Wiegman (PerimeterX San Mateo), Gal Weizman (PerimterX Tel Aviv)
+// Time of Creation (most recent version): 01 November 2020 03:08 [UTC]
+// Extra: Handily adds a function to format the output directly as JSON and put the result into your clipboard, for easy export to file.
+// Web: On the web @ JSFiddle -- https://jsfiddle.net/4jcazrf8/1/
+
+//Write guidance to the webpage -- if you want to overwrite DOM, uncomment the below
+//document.body.innerHTML = `<h1>${'Open the Console in the Developer Tools to see the result'}</h1>`;
+
+//Optional Console Logging - Descriptive Description is Descriptive?
+//console.log('Every event supported by every object in the browser:')
+
+function _isEvent(prop) {
+    return 0 === prop.indexOf("on");
+}
+
+function _getEvents(obj) {
+    const result = [];
+
+    for (var prop in obj) {
+        if (_isEvent(prop)) {
+            prop = prop.substr(2); // remove "on" at the beginning
+            result.push(prop);
+        }
+    }
+
+    return result;
+}
+
+function getEvents() {
+    const result = {};
+
+    result["window"] = _getEvents(window, hasOwnProperty);
+
+    const arr = Object.getOwnPropertyNames(window);
+
+    let proto;
+    for (let i = 0; i < arr.length; i++) {
+        const element = arr[i];
+
+        let resultArray = [];
+
+        try {
+            const obj = window[element];
+
+            if (!obj || !obj["prototype"]) {
+                continue;
+            }
+
+            proto = obj["prototype"];
+
+            resultArray = _getEvents(proto);
+
+        } catch (err) {
+            // console.error(`failed to get events of %o`, element);
+        }
+
+        result[element] = resultArray;
+    }
+
+    return result;
+}
+
+function hasOwnProperty() {
+}
+
+//show the result in your browser
+console.log(JSON.stringify(getEvents()));
+
+//Copy a JSON of the output of all events in the browser
+var consoleOutput = JSON.stringify(getEvents());
+
+copy(consoleOutput);
+
+//optional couple of lines, it helps suppress a few linter errors
+function copy(consoleOutput) {
+}