Sapper: target="_self" on <a> causes full page load
With the following
<a href="/" target="_self">Link</a>
it does a full page load of '/'
_self is the default so I would expect having it set not to make any difference
UnwrittenFun
All 4 comments
I believe this is intentional (though perhaps it ought to be documented). When a routing system works by intercepting clicks on links, using target='_self' on a link is a semi-standard way to let the routing system know that this link _should_ force a page load, even if its href looks like it could be part of the same app.
Conduitry
on 10 May 2018
Should definitely be documented if intended 馃憤
I ran into this as an issue where I had a Button component which could be an a or button tag depending on if href was specified, I passed through target to the element with a default to _self as otherwise it would set it to undefined which always opens in a new tab.
UnwrittenFun
on 10 May 2018
Yes, it's intentional. An addition to the documentation would be awesome.
EmilTholin
on 10 May 2018
Closing in favour of https://github.com/sveltejs/sapper.svelte.technology/issues/31
Rich-Harris
on 3 Sep 2018
Related issues
freedmand
路
4Comments
benmccann
路
3Comments
Rich-Harris
路
3Comments
keyvan-m-sadeghi
路
4Comments
Snugug
路
4Comments
Most helpful comment
I believe this is intentional (though perhaps it ought to be documented). When a routing system works by intercepting clicks on links, using
target='_self'on a link is a semi-standard way to let the routing system know that this link _should_ force a page load, even if its href looks like it could be part of the same app.