Why not to interact with the DOM directly in Angular?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
I have read that it is not wise to interact with the DOM directly both for security and performance. Avoiding using syntax like below to select Elements.
const itemToManipulate = document.getElementById('example');
So I read a good work around is to use ElementRef Directive.
But go on to find the Angular Documents advise against this because of tight coupling, what is tight coupling?
Found in documentation here
I settled for using a ViewChild, like so...
@ViewChild('itemToManipulate') public item: ElementRef<any>;
Does this lead to any unwanted behaviour I should be concerned about (security / performance wise) and is there a best practice for interacting with the DOM, or should this not be done within Angular (6 / 7)?
Thanks in Advance.
angular dom asked Nov 23 '18 at 19:14
dince12dince12
1,4431721
add a comment |
I have read that it is not wise to interact with the DOM directly both for security and performance. Avoiding using syntax like below to select Elements.
const itemToManipulate = document.getElementById('example');
So I read a good work around is to use ElementRef Directive.
But go on to find the Angular Documents advise against this because of tight coupling, what is tight coupling?
Found in documentation here
I settled for using a ViewChild, like so...
@ViewChild('itemToManipulate') public item: ElementRef<any>;
Does this lead to any unwanted behaviour I should be concerned about (security / performance wise) and is there a best practice for interacting with the DOM, or should this not be done within Angular (6 / 7)?
Thanks in Advance.
angular dom asked Nov 23 '18 at 19:14
dince12dince12
1,4431721
2
Could you also add the links that you referred on the Angular Docs to the OP?
– SiddAjmera
Nov 23 '18 at 19:18
5
Highly recommend to watch Can't Touch This! What not to do to the DOM
– Pankaj Parkar
Nov 23 '18 at 19:19
1
in addition to @PankajParkar's video which you should definitely watch, there's a big security risk in directly manipulating the dom, via renderer or native, a manual sanitation is required on many cases. so in short, don't go that way. stick to the angular way of doing stuff.
– Stavm
Feb 2 at 8:03
add a comment |
I have read that it is not wise to interact with the DOM directly both for security and performance. Avoiding using syntax like below to select Elements.
const itemToManipulate = document.getElementById('example');
So I read a good work around is to use ElementRef Directive.
But go on to find the Angular Documents advise against this because of tight coupling, what is tight coupling?
Found in documentation here
I settled for using a ViewChild, like so...
@ViewChild('itemToManipulate') public item: ElementRef<any>;
Does this lead to any unwanted behaviour I should be concerned about (security / performance wise) and is there a best practice for interacting with the DOM, or should this not be done within Angular (6 / 7)?
Thanks in Advance.
angular dom asked Nov 23 '18 at 19:14
dince12dince12
1,4431721
I have read that it is not wise to interact with the DOM directly both for security and performance. Avoiding using syntax like below to select Elements.
const itemToManipulate = document.getElementById('example');
So I read a good work around is to use ElementRef Directive.
But go on to find the Angular Documents advise against this because of tight coupling, what is tight coupling?
Found in documentation here
I settled for using a ViewChild, like so...
@ViewChild('itemToManipulate') public item: ElementRef<any>;
Does this lead to any unwanted behaviour I should be concerned about (security / performance wise) and is there a best practice for interacting with the DOM, or should this not be done within Angular (6 / 7)?
Thanks in Advance.
angular dom angular dom asked Nov 23 '18 at 19:14
dince12dince12
1,4431721
asked Nov 23 '18 at 19:14
dince12dince12
1,4431721
edited Mar 3 at 11:27
dince12
asked Nov 23 '18 at 19:14
dince12dince12
1,4431721
asked Nov 23 '18 at 19:14
dince12dince12
1,4431721
asked Nov 23 '18 at 19:14
dince12dince12
1,4431721
1,4431721
2
Could you also add the links that you referred on the Angular Docs to the OP?
– SiddAjmera
Nov 23 '18 at 19:18
5
Highly recommend to watch Can't Touch This! What not to do to the DOM
– Pankaj Parkar
Nov 23 '18 at 19:19
1
in addition to @PankajParkar's video which you should definitely watch, there's a big security risk in directly manipulating the dom, via renderer or native, a manual sanitation is required on many cases. so in short, don't go that way. stick to the angular way of doing stuff.
– Stavm
Feb 2 at 8:03
add a comment |
2
Could you also add the links that you referred on the Angular Docs to the OP?
– SiddAjmera
Nov 23 '18 at 19:18
5
Highly recommend to watch Can't Touch This! What not to do to the DOM
– Pankaj Parkar
Nov 23 '18 at 19:19
1
in addition to @PankajParkar's video which you should definitely watch, there's a big security risk in directly manipulating the dom, via renderer or native, a manual sanitation is required on many cases. so in short, don't go that way. stick to the angular way of doing stuff.
– Stavm
Feb 2 at 8:03
2
2
Could you also add the links that you referred on the Angular Docs to the OP?
– SiddAjmera
Nov 23 '18 at 19:18
Could you also add the links that you referred on the Angular Docs to the OP?
– SiddAjmera
Nov 23 '18 at 19:18
5
5
Highly recommend to watch Can't Touch This! What not to do to the DOM
– Pankaj Parkar
Nov 23 '18 at 19:19
Highly recommend to watch Can't Touch This! What not to do to the DOM
– Pankaj Parkar
Nov 23 '18 at 19:19
1
1
in addition to @PankajParkar's video which you should definitely watch, there's a big security risk in directly manipulating the dom, via renderer or native, a manual sanitation is required on many cases. so in short, don't go that way. stick to the angular way of doing stuff.
– Stavm
Feb 2 at 8:03
in addition to @PankajParkar's video which you should definitely watch, there's a big security risk in directly manipulating the dom, via renderer or native, a manual sanitation is required on many cases. so in short, don't go that way. stick to the angular way of doing stuff.
– Stavm
Feb 2 at 8:03
add a comment |
0
active
oldest
votes
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%2f53451918%2fwhy-not-to-interact-with-the-dom-directly-in-angular%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f53451918%2fwhy-not-to-interact-with-the-dom-directly-in-angular%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
2
Could you also add the links that you referred on the Angular Docs to the OP?
– SiddAjmera
Nov 23 '18 at 19:18
5
Highly recommend to watch Can't Touch This! What not to do to the DOM
– Pankaj Parkar
Nov 23 '18 at 19:19
1
in addition to @PankajParkar's video which you should definitely watch, there's a big security risk in directly manipulating the dom, via renderer or native, a manual sanitation is required on many cases. so in short, don't go that way. stick to the angular way of doing stuff.
– Stavm
Feb 2 at 8:03