juicy / juicy-redirect Goto Github PK

It seems, with Palindrom/palindrom-redirect used for most of our cases, there is no much need for this element. Then given our short resources, it could be a good idea to drop support for it.

Please vote with reactions

• 👍 drop support,
• 👎 keep it, then comment on your needs,
• 😕 if you would like to have some transition period/release with a warning or smth else.

//cc @Starcounter/webplatformteam

There is a problem with the history attribute in juicy-redirect - it has no effect in PuppetJS.

For that, you need to use link is="puppet-redirect" history.

It is too simple to make a mistake of using link is="juicy-redirect" history, so we have 2 options:

1. remove the history attribute from juicy-redirect
2. merge puppet-redirect features into PuppetDOM and then discontinue puppet-redirect

I would like to use juicy-redirect when an URL should be morphed but no request should be sent to the server. Is the intended functionality / is this functionality possible? @tomalec @miyconst @warpech

Steps to reproduce

1. Fire up the Live Demo
2. Press the button <link is="juicy-redirect" url="/">

Expected result

To still show the Live Demo page but the URL should have been changed (at least I thought so)

Actual result

404 File not found

Browsers affected

• [x ] Chrome
• Firefox
• Edge
• Safari 9
• Safari 8
• IE 11

Screenshot

Add the ability to redirect to a new window with some new attribute like the target attribute on <a>

Example:
<link is="juicy-redirect" target="_blank" url="http://www.google.com"></juicy-redirect>

This repo uses .bowerrc file which causes it to act arcane - when you type bower install, the dependencies get installed in the parent directory.

Proposed solution - remove .bowerrc and recommend using polyserve.

Same thing was done in Juicy/juicy-select#8