RouterLink in Angular using Javascript
I am trying to use a javascript method similar to routerLink
in HTML but using Javascript.
I have tried with window.location
but the result is not the same since this command refreshes the website to jump from one URL to another. Is there any possibility to jump from a component to another one as routerLink
does (not refreshing)?
Solution
I was asking for router.navigateByUrl('/url')
javascript angular
add a comment |
I am trying to use a javascript method similar to routerLink
in HTML but using Javascript.
I have tried with window.location
but the result is not the same since this command refreshes the website to jump from one URL to another. Is there any possibility to jump from a component to another one as routerLink
does (not refreshing)?
Solution
I was asking for router.navigateByUrl('/url')
javascript angular
add a comment |
I am trying to use a javascript method similar to routerLink
in HTML but using Javascript.
I have tried with window.location
but the result is not the same since this command refreshes the website to jump from one URL to another. Is there any possibility to jump from a component to another one as routerLink
does (not refreshing)?
Solution
I was asking for router.navigateByUrl('/url')
javascript angular
I am trying to use a javascript method similar to routerLink
in HTML but using Javascript.
I have tried with window.location
but the result is not the same since this command refreshes the website to jump from one URL to another. Is there any possibility to jump from a component to another one as routerLink
does (not refreshing)?
Solution
I was asking for router.navigateByUrl('/url')
javascript angular
javascript angular
edited Nov 15 '18 at 17:26
Mario
asked Nov 15 '18 at 14:46
MarioMario
4142524
4142524
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The routerLink
's directive internal implementation doesn't use the window.location
API, but the window.history
API, the window.history.pushState()
function to be more precise (Source).
Same goes for every SPA Framework.
add a comment |
It's window.location.hash
that you can change without reloading. That can be used to create an SPA as well if you don't want to mess with history.pushState()
window.addEventListener( 'hashchange', event => {
console.log( `should render page: ${ window.location.hash }` )
});
<a href="#/home">Home</a>
<a href="#/page1">Page 1</a>
<a href="#/page2">Page 2</a>
<a href="#/page3">Page 3</a>
This does have other downsides compared to history.pushState()
, like search engine optimalization and such. But it's the simplest method to do single page app routing. So kinda depends on what you're building if it'll suffice or not.
If you're using angular though, just use the routing angular provides.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321987%2frouterlink-in-angular-using-javascript%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The routerLink
's directive internal implementation doesn't use the window.location
API, but the window.history
API, the window.history.pushState()
function to be more precise (Source).
Same goes for every SPA Framework.
add a comment |
The routerLink
's directive internal implementation doesn't use the window.location
API, but the window.history
API, the window.history.pushState()
function to be more precise (Source).
Same goes for every SPA Framework.
add a comment |
The routerLink
's directive internal implementation doesn't use the window.location
API, but the window.history
API, the window.history.pushState()
function to be more precise (Source).
Same goes for every SPA Framework.
The routerLink
's directive internal implementation doesn't use the window.location
API, but the window.history
API, the window.history.pushState()
function to be more precise (Source).
Same goes for every SPA Framework.
answered Nov 15 '18 at 14:48
YoukouleleYYoukouleleY
2,7701827
2,7701827
add a comment |
add a comment |
It's window.location.hash
that you can change without reloading. That can be used to create an SPA as well if you don't want to mess with history.pushState()
window.addEventListener( 'hashchange', event => {
console.log( `should render page: ${ window.location.hash }` )
});
<a href="#/home">Home</a>
<a href="#/page1">Page 1</a>
<a href="#/page2">Page 2</a>
<a href="#/page3">Page 3</a>
This does have other downsides compared to history.pushState()
, like search engine optimalization and such. But it's the simplest method to do single page app routing. So kinda depends on what you're building if it'll suffice or not.
If you're using angular though, just use the routing angular provides.
add a comment |
It's window.location.hash
that you can change without reloading. That can be used to create an SPA as well if you don't want to mess with history.pushState()
window.addEventListener( 'hashchange', event => {
console.log( `should render page: ${ window.location.hash }` )
});
<a href="#/home">Home</a>
<a href="#/page1">Page 1</a>
<a href="#/page2">Page 2</a>
<a href="#/page3">Page 3</a>
This does have other downsides compared to history.pushState()
, like search engine optimalization and such. But it's the simplest method to do single page app routing. So kinda depends on what you're building if it'll suffice or not.
If you're using angular though, just use the routing angular provides.
add a comment |
It's window.location.hash
that you can change without reloading. That can be used to create an SPA as well if you don't want to mess with history.pushState()
window.addEventListener( 'hashchange', event => {
console.log( `should render page: ${ window.location.hash }` )
});
<a href="#/home">Home</a>
<a href="#/page1">Page 1</a>
<a href="#/page2">Page 2</a>
<a href="#/page3">Page 3</a>
This does have other downsides compared to history.pushState()
, like search engine optimalization and such. But it's the simplest method to do single page app routing. So kinda depends on what you're building if it'll suffice or not.
If you're using angular though, just use the routing angular provides.
It's window.location.hash
that you can change without reloading. That can be used to create an SPA as well if you don't want to mess with history.pushState()
window.addEventListener( 'hashchange', event => {
console.log( `should render page: ${ window.location.hash }` )
});
<a href="#/home">Home</a>
<a href="#/page1">Page 1</a>
<a href="#/page2">Page 2</a>
<a href="#/page3">Page 3</a>
This does have other downsides compared to history.pushState()
, like search engine optimalization and such. But it's the simplest method to do single page app routing. So kinda depends on what you're building if it'll suffice or not.
If you're using angular though, just use the routing angular provides.
window.addEventListener( 'hashchange', event => {
console.log( `should render page: ${ window.location.hash }` )
});
<a href="#/home">Home</a>
<a href="#/page1">Page 1</a>
<a href="#/page2">Page 2</a>
<a href="#/page3">Page 3</a>
window.addEventListener( 'hashchange', event => {
console.log( `should render page: ${ window.location.hash }` )
});
<a href="#/home">Home</a>
<a href="#/page1">Page 1</a>
<a href="#/page2">Page 2</a>
<a href="#/page3">Page 3</a>
answered Nov 15 '18 at 14:54
ShillyShilly
5,7181716
5,7181716
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53321987%2frouterlink-in-angular-using-javascript%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown