Page visibility bugs

.eslintrc

@@ -5,10 +5,23 @@
     "node": true,
   },
   "parserOptions": {
+    "ecmaVersion": 2017,
     "sourceType": "module",
   },
   "extends": [
     "eslint:recommended",
     "google",
   ],
+  "globals": {
+    "safari": false
+  },
+  "overrides": [
+    {
+      "files": ["test/**/*"],
+      "globals": {
+        "assert": false,
+        "sinon": false
+      }
+    }
+  ]
 }

.travis.yml

@@ -1,7 +1,7 @@
 ---
 language: node_js
 node_js:
-  - "6"
+  - "node"
 
 # If a valid commit range exits, check that it has changes to code files.
 before_install:

CHANGELOG.md

@@ -2,6 +2,18 @@
 
 This document lists the changes between each minor and patch versions. For changes between major versions, see the [Upgrade Reference](/docs/upgrading.md)
 
+### 2.4.1 (2017-06-07)
+
+- Fix a bug in Safari where `outboundLinkTracker` doesn't work with the back button [#185]
+
+### 2.4.0 (2017-06-02)
+
+- Add a `queryParamsWhitelist` option to the `cleanUrlTracker` plugin [#181]
+
+### 2.3.3 (2017-05-23)
+
+- Fix a bug where, in rare cases, visibility times were being tracked cross-session [#177]
+
 ### 2.3.2 (2017-04-10)
 
 - Fix incorrect plugin usage attribution on the initial pageview sent by the `pageVisibilityTracker` if other plugins are required after it [#169]

README.md

@@ -1,3 +1,5 @@
+# This library is no longer actively maintained
+
 # Autotrack [![Build Status](https://travis-ci.org/googleanalytics/autotrack.svg?branch=master)](https://travis-ci.org/googleanalytics/autotrack)
 
 - [Overview](#overview)
@@ -21,7 +23,7 @@ Autotrack was created to solve this problem. It provides default tracking for th
 
 ## Plugins
 
-The `autotrack.js` file in this repository is small (7K gzipped) and comes with all plugins included. You can use it as is, or you can create a [custom build](#custom-builds) that only includes the plugins you want to make it even smaller.
+The `autotrack.js` file in this repository is small (8K gzipped) and comes with all plugins included. You can use it as is, or you can create a [custom build](#custom-builds) that only includes the plugins you want to make it even smaller.
 
 The following table briefly explains what each plugin does; you can click on the plugin name to see the full documentation and usage instructions:
 
@@ -72,7 +74,7 @@ The following table briefly explains what each plugin does; you can click on the
   </tr>
 </table>
 
-**Disclaimer:** autotrack is maintained by members of the Google Analytics developer platform team and is primarily intended for a developer audience. It is not an official Google Analytics product and does not qualify for Google Analytics 360 support. Developers who choose to use this library are responsible for ensuring that their implementation meets the requirements of the [Google Analytics Terms of Service](https://www.google.com/analytics/terms/us.html) and the legal obligations of their respective country.
+**Disclaimer:** autotrack is maintained by members of the Google Analytics developer platform team and is primarily intended for a developer audience. It is not an official Google Analytics product and does not qualify for Google Analytics 360 support. Developers who choose to use this library are responsible for ensuring that their implementation meets the requirements of the [Google Analytics Terms of Service](https://marketingplatform.google.com/about/analytics/terms/us/) and the legal obligations of their respective country.
 
 ## Installation and usage
 
@@ -110,7 +112,7 @@ Of course, you'll have to make the following modifications to the above code to
 
 ### Loading autotrack via npm
 
-If you use npm and a module loader that understands [ES2015 imports](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import) (e.g. [Webpack](https://webpack.js.org/), [Rollup](http://rollupjs.org/), or [SystemJS](https://github.com/systemjs/systemjs)), you can include autotrack in your build by importing it as you would any other npm module:
+If you use npm and a module loader that understands [ES2015 imports](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import) (e.g. [Webpack](https://webpack.js.org/), [Rollup](https://rollupjs.org/), or [SystemJS](https://github.com/systemjs/systemjs)), you can include autotrack in your build by importing it as you would any other npm module:
 
 ```sh
 npm install autotrack
@@ -277,7 +279,7 @@ The following translations have been graciously provided by the community. Pleas
 If you discover issues with a particular translation, please file them with the appropriate repository. To submit your own translation, follow these steps:
 
 1. Fork this repository.
-2. Update the settings of your fork to [allow issues](http://programmers.stackexchange.com/questions/179468/forking-a-repo-on-github-but-allowing-new-issues-on-the-fork).
+2. Update the settings of your fork to [allow issues](https://softwareengineering.stackexchange.com/questions/179468/forking-a-repo-on-github-but-allowing-new-issues-on-the-fork).
 3. Remove all non-documentation files.
 4. Update the documentation files with your translated versions.
 5. Submit a pull request to this repository that adds a link to your fork to the above list.