🔥 Remove polyfills

These are better done by the application using the elements.

Author: NeoLegends

README.md

@@ -4,8 +4,9 @@ A Polymer 2.0 Element that performs the OAuth2 authorization code flow using a p
 
 ## Usage
 
-1. Set up your OAuth2 config properly (Client ID, Redirect URL, etc.)
-2. Include the `oauth-authorizator` element on your page like this:
+1. Properly polyfill [`URL`][1], [`URLSearchParams`][2] and [`fetch`][3], so that `fetch` can work with `URLSearchParams`-objects. `<oauth-receiver>` only needs [`URLSearchParams`][2].
+2. Set up your OAuth2 config properly (Client ID, Redirect URL, etc.)
+3. Include the `oauth-authorizator` element on your page like this:
 ```html
 <oauth-authorizator access-token="{{yourAccessToken}}"
                     authorization-url="The URL that will be loaded in the popup window, e.g. https://accounts.spotify.com/authorize"
@@ -16,15 +17,19 @@ A Polymer 2.0 Element that performs the OAuth2 authorization code flow using a p
                     token-refresh-url="The URL where your token refresh server is located">
 </oauth-authorizator>
 ```
-3. Set up the `oauth-receiver` on the redirect page
+4. Set up the `oauth-receiver` on the redirect page
 ```html
 <oauth-receiver target="Optional, the site you're hosting your website on. E.g. https://festify.us"></oauth-receiver>
 ```
-4. Call `oauth-authorizator.login()` at the appropriate time to start the authorization process. The access token will appear as observable property at `oauth-authorizator.accessToken` or will be available through the Promise's return value.
+5. Call `oauth-authorizator.login()` at the appropriate time to start the authorization process. The access token will appear as observable property at `oauth-authorizator.accessToken` or will be available through the Promise's return value.
 
 ## Manual Mode
 
 If you set the `manual`-attribute on `<oauth-receiver>`, the element will not attempt to parse the parameters on page load. Instead, you will need to call `<oauth-receiver>.receive()` in order to parse and send the OAuth get parameters. This could be useful if you want to show the user some content before redirecting back to the application.
 
 ## License
 MIT
+
+[1]: https://developer.mozilla.org/en-US/docs/Web/API/URL
+[2]: https://developer.mozilla.org/en-US/docs/Web/API/URLSearchParams
+[3]: https://developer.mozilla.org/en-US/docs/Web/API/GlobalFetch/fetch

bower.json

@@ -3,10 +3,7 @@
   "description": "A Polymer 2.0 Element that performs the OAuth2 authorization code flow",
   "main": "oauth-authorizator.html",
   "dependencies": {
-    "fetch-import": "^1.0.0",
-    "polymer": "Polymer/polymer#^2.0.0",
-    "url": "webcomponents/URL#^0.5.7",
-    "url-search-params": "^0.9.0"
+    "polymer": "Polymer/polymer#^2.0.0"
   },
   "devDependencies": {
     "iron-demo-helpers": "PolymerElements/iron-demo-helpers#^2.0.0",

oauth-authorizator.html

@@ -1,7 +1,4 @@
 <link rel="import" href="../polymer/polymer-element.html">
-<link rel="import" href="url-search-params-polyfill.html"> <!-- Must come before fetch polyfill -->
-<link rel="import" href="../fetch-import/fetch.html">
-<link rel="import" href="url-polyfill.html">
 
 <script>
     /**

oauth-receiver.html

@@ -1,5 +1,3 @@
-<link rel="import" href="url-search-params-polyfill.html">
-
 <script>
     /**
      * `oauth-receiver`