document.getElementById(“myId”) vs component.find(“myId”).getElement();
What is better to use document.getElementById("myId") or component.find("myId").getElement(); in terms of performance? What will be faster?
lightning-aura-components lightning id aura-id
asked Nov 21 '18 at 16:57
yourbuddyyourbuddy
534
add a comment |
What is better to use document.getElementById("myId") or component.find("myId").getElement(); in terms of performance? What will be faster?
lightning-aura-components lightning id aura-id
asked Nov 21 '18 at 16:57
yourbuddyyourbuddy
534
add a comment |
What is better to use document.getElementById("myId") or component.find("myId").getElement(); in terms of performance? What will be faster?
lightning-aura-components lightning id aura-id
asked Nov 21 '18 at 16:57
yourbuddyyourbuddy
534
What is better to use document.getElementById("myId") or component.find("myId").getElement(); in terms of performance? What will be faster?
lightning-aura-components lightning id aura-id
lightning-aura-components lightning id aura-id
asked Nov 21 '18 at 16:57
yourbuddyyourbuddy
534
asked Nov 21 '18 at 16:57
yourbuddyyourbuddy
534
asked Nov 21 '18 at 16:57
yourbuddyyourbuddy
534
asked Nov 21 '18 at 16:57
yourbuddyyourbuddy
534
asked Nov 21 '18 at 16:57
yourbuddyyourbuddy
534
534
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Regardless of performance, you should use component.find. Document query selectors aren't recommended in lightning, whereas component.find has explicit support:
Valid DOM Access
The following methods are valid DOM access because the elements are created by
c:domLocker.
cmp.getElements()
Returns the elements in the DOM rendered by the component.
cmp.find()
Returns the div and button components, identified by their aura:id attributes.
cmp.find("div1").getElement()
Returns the DOM element for the div as c:domLocker created the div.
event.getSource().get("v.name")
Returns the name of the button that dispatched the event; in this case, myButton.
Notice the complete absence of query selectors in the enumeration of valid methods to access the DOM. It's not a supported approach, strictly speaking, even if it may work today.
answered Nov 21 '18 at 17:02
Adrian Larson♦Adrian Larson
105k19112236
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fsalesforce.stackexchange.com%2fquestions%2f240146%2fdocument-getelementbyidmyid-vs-component-findmyid-getelement%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Regardless of performance, you should use component.find. Document query selectors aren't recommended in lightning, whereas component.find has explicit support:
Valid DOM Access
The following methods are valid DOM access because the elements are created by
c:domLocker.
cmp.getElements()
Returns the elements in the DOM rendered by the component.
cmp.find()
Returns the div and button components, identified by their aura:id attributes.
cmp.find("div1").getElement()
Returns the DOM element for the div as c:domLocker created the div.
event.getSource().get("v.name")
Returns the name of the button that dispatched the event; in this case, myButton.
Notice the complete absence of query selectors in the enumeration of valid methods to access the DOM. It's not a supported approach, strictly speaking, even if it may work today.
answered Nov 21 '18 at 17:02
Adrian Larson♦Adrian Larson
105k19112236
add a comment |
Regardless of performance, you should use component.find. Document query selectors aren't recommended in lightning, whereas component.find has explicit support:
Valid DOM Access
The following methods are valid DOM access because the elements are created by
c:domLocker.
cmp.getElements()
Returns the elements in the DOM rendered by the component.
cmp.find()
Returns the div and button components, identified by their aura:id attributes.
cmp.find("div1").getElement()
Returns the DOM element for the div as c:domLocker created the div.
event.getSource().get("v.name")
Returns the name of the button that dispatched the event; in this case, myButton.
Notice the complete absence of query selectors in the enumeration of valid methods to access the DOM. It's not a supported approach, strictly speaking, even if it may work today.
answered Nov 21 '18 at 17:02
Adrian Larson♦Adrian Larson
105k19112236
add a comment |
Regardless of performance, you should use component.find. Document query selectors aren't recommended in lightning, whereas component.find has explicit support:
Valid DOM Access
The following methods are valid DOM access because the elements are created by
c:domLocker.
cmp.getElements()
Returns the elements in the DOM rendered by the component.
cmp.find()
Returns the div and button components, identified by their aura:id attributes.
cmp.find("div1").getElement()
Returns the DOM element for the div as c:domLocker created the div.
event.getSource().get("v.name")
Returns the name of the button that dispatched the event; in this case, myButton.
Notice the complete absence of query selectors in the enumeration of valid methods to access the DOM. It's not a supported approach, strictly speaking, even if it may work today.
answered Nov 21 '18 at 17:02
Adrian Larson♦Adrian Larson
105k19112236
Regardless of performance, you should use component.find. Document query selectors aren't recommended in lightning, whereas component.find has explicit support:
Valid DOM Access
The following methods are valid DOM access because the elements are created by
c:domLocker.
cmp.getElements()
Returns the elements in the DOM rendered by the component.
cmp.find()
Returns the div and button components, identified by their aura:id attributes.
cmp.find("div1").getElement()
Returns the DOM element for the div as c:domLocker created the div.
event.getSource().get("v.name")
Returns the name of the button that dispatched the event; in this case, myButton.
Notice the complete absence of query selectors in the enumeration of valid methods to access the DOM. It's not a supported approach, strictly speaking, even if it may work today.
answered Nov 21 '18 at 17:02
Adrian Larson♦Adrian Larson
105k19112236
answered Nov 21 '18 at 17:02
Adrian Larson♦Adrian Larson
105k19112236
answered Nov 21 '18 at 17:02
Adrian Larson♦Adrian Larson
105k19112236
answered Nov 21 '18 at 17:02
Adrian Larson♦Adrian Larson
105k19112236
105k19112236
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fsalesforce.stackexchange.com%2fquestions%2f240146%2fdocument-getelementbyidmyid-vs-component-findmyid-getelement%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
