Make it work while disconnected from DOM

Fixed a bug when the url property or attribute was set while palindrom-redirect is not connected to DOM.

With this fix, palindrom-redirect will perform the redirection once connected to DOM.

Make it work in shadow DOM

See #10

Autonomous Custom Element v1

• Changed the API to use Custom Elements V1,
• Changed to autonomous elements, due to lack of polyfill support for customized built-ins,
  ⚠️ Please update your code to use <palindrom-redirect> instead of <link is="palindrom-redirect">.
• Dropped backward compatibility with puppet-redirect,
• Updated behavior for url property set to null (same as removeAttribute).

See #9

Dispatch proper event upon redirect

palindrom-redirect used to dispatch two events (palindrom-redirect-pushstate and puppet-redirect-pushstate) and this trigger Palindrom redirection twice causing a redundant request. From now on, it will dispatch a single event that matches its is attribute (palindrom-redirect-pushstate or puppet-redirect-pushstate).

Redirection after redirection fix

Release after merge with 0.6.0 version of Juicy/juicy-redirect

Rename to palindrom-redirect and deprecate puppet-redirect

0.5.0

Version 0.5.0

`target` attribute

was added, to open pages in new tabs

0.1.3

Merge back changes from juicy-redirect 0.1.3:

• Removed dependency on platform.js in bower.json