rebase

CHANGELOG.md

@@ -28,6 +28,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - Unused normalize.css file
   
 -->
+## [2.27.3]
+
+### Changed
+
+- Fixes a rare condition with UMD where we assume rg4js is initialised but it is not, causing an infinite loop.
+
 
 
 ## [2.27.2]

bower.json

@@ -1,6 +1,6 @@
 {
   "name": "raygun4js",
-  "version": "2.27.2",
+  "version": "2.27.3",
   "homepage": "http://raygun.com",
   "authors": [
     "Mindscape <[email protected]>"

package.json

@@ -6,7 +6,7 @@
   ],
   "title": "Raygun4js",
   "description": "Raygun.com plugin for JavaScript",
-  "version": "2.27.2",
+  "version": "2.27.3",
   "homepage": "https://github.com/MindscapeHQ/raygun4js",
   "author": {
     "name": "MindscapeHQ",

raygun4js.nuspec

@@ -2,7 +2,7 @@
 <package xmlns="http://schemas.microsoft.com/packaging/2010/07/nuspec.xsd">
   <metadata>
     <id>raygun4js</id>
-    <version>2.27.2</version>
+    <version>2.27.3</version>
     <title>Raygun4js</title>
     <authors>Raygun Limited</authors>
     <owners>Raygun Limited</owners>

tests/specs/v2/UMDInfiniteLoopTest.js

@@ -1,5 +1,19 @@
 var webdriverio = require('webdriverio');
 
+
+
+
+/**
+* What does this test do?
+* When using the UMD module, if raygun events are fired (e.g. rg4js('send', ...)) 
+* before raygun is fully loaded they are stored in an object on the window.
+* When Raygun loads these are then processed.
+* However a bug was found where we were assuming raygun was loaded when 
+* `document.readyState === complete` but it is not loaded until slightly 
+* after when the `load` event is fired. This means that if a rayugn event 
+* is processed in this gap an infinite loop can be caused.
+* This test ensures graceful handling of this situation
+*/
 describe("UMD Infinite loop test", function() {
     beforeEach(async function() {
         /**