How can I use Lightning:input focus on init?
Not sure what am i missing here but trying few approaches but still having some issues and it doesn't work so far.
How can I invoke the method focus on a ui input :
cmp
<lightning:input label="Name" aura:id="itemName" value="{!v.item.Name}" required="true" />
js
var nameInput = component.find('itemName');
nameInput.focus();
Also tried
component.find('itemName').getElement().focus();
lightning-aura-components lightninginput
add a comment |
Not sure what am i missing here but trying few approaches but still having some issues and it doesn't work so far.
How can I invoke the method focus on a ui input :
cmp
<lightning:input label="Name" aura:id="itemName" value="{!v.item.Name}" required="true" />
js
var nameInput = component.find('itemName');
nameInput.focus();
Also tried
component.find('itemName').getElement().focus();
lightning-aura-components lightninginput
add a comment |
Not sure what am i missing here but trying few approaches but still having some issues and it doesn't work so far.
How can I invoke the method focus on a ui input :
cmp
<lightning:input label="Name" aura:id="itemName" value="{!v.item.Name}" required="true" />
js
var nameInput = component.find('itemName');
nameInput.focus();
Also tried
component.find('itemName').getElement().focus();
lightning-aura-components lightninginput
Not sure what am i missing here but trying few approaches but still having some issues and it doesn't work so far.
How can I invoke the method focus on a ui input :
cmp
<lightning:input label="Name" aura:id="itemName" value="{!v.item.Name}" required="true" />
js
var nameInput = component.find('itemName');
nameInput.focus();
Also tried
component.find('itemName').getElement().focus();
lightning-aura-components lightninginput
lightning-aura-components lightninginput
asked Dec 20 '18 at 20:27
sfdx bombsfdx bomb
684614
684614
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
This might just be a matter of dom load timing! There are couple of ways you can make it work.
- Adding a timer
- Using after renderer
Adding a timer
window.setTimeout(
$A.getCallback(function () {
cmp.find("itemName").focus();
}), 1
);
Renderer Approach:
afterRender: function (cmp, helper) {
this.superAfterRender();
cmp.find("itemName").focus();
}
I like the Renderer approach and using it now. weird that it's not working on simple controller init. Thanks !
– sfdx bomb
Dec 20 '18 at 21:05
I agree andthis.superAfterRender();
will ensure all the default component rendering! This is something similar on Lightning data service and I usually use attribute change handlers in that case!
– codeyinthecloud
Dec 20 '18 at 21:07
+1 but instead ofafterRender
,render
is the easier and preferred approach.
– Jayant Das
Dec 20 '18 at 22:26
@JayantDas Thanks for the suggestion, the reason I went with afterRender is doc states method is called to enable you to interact with the DOM tree after the framework’s rendering service has inserted DOM elements.
– codeyinthecloud
Dec 20 '18 at 22:31
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%2f244368%2fhow-can-i-use-lightninginput-focus-on-init%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
This might just be a matter of dom load timing! There are couple of ways you can make it work.
- Adding a timer
- Using after renderer
Adding a timer
window.setTimeout(
$A.getCallback(function () {
cmp.find("itemName").focus();
}), 1
);
Renderer Approach:
afterRender: function (cmp, helper) {
this.superAfterRender();
cmp.find("itemName").focus();
}
I like the Renderer approach and using it now. weird that it's not working on simple controller init. Thanks !
– sfdx bomb
Dec 20 '18 at 21:05
I agree andthis.superAfterRender();
will ensure all the default component rendering! This is something similar on Lightning data service and I usually use attribute change handlers in that case!
– codeyinthecloud
Dec 20 '18 at 21:07
+1 but instead ofafterRender
,render
is the easier and preferred approach.
– Jayant Das
Dec 20 '18 at 22:26
@JayantDas Thanks for the suggestion, the reason I went with afterRender is doc states method is called to enable you to interact with the DOM tree after the framework’s rendering service has inserted DOM elements.
– codeyinthecloud
Dec 20 '18 at 22:31
add a comment |
This might just be a matter of dom load timing! There are couple of ways you can make it work.
- Adding a timer
- Using after renderer
Adding a timer
window.setTimeout(
$A.getCallback(function () {
cmp.find("itemName").focus();
}), 1
);
Renderer Approach:
afterRender: function (cmp, helper) {
this.superAfterRender();
cmp.find("itemName").focus();
}
I like the Renderer approach and using it now. weird that it's not working on simple controller init. Thanks !
– sfdx bomb
Dec 20 '18 at 21:05
I agree andthis.superAfterRender();
will ensure all the default component rendering! This is something similar on Lightning data service and I usually use attribute change handlers in that case!
– codeyinthecloud
Dec 20 '18 at 21:07
+1 but instead ofafterRender
,render
is the easier and preferred approach.
– Jayant Das
Dec 20 '18 at 22:26
@JayantDas Thanks for the suggestion, the reason I went with afterRender is doc states method is called to enable you to interact with the DOM tree after the framework’s rendering service has inserted DOM elements.
– codeyinthecloud
Dec 20 '18 at 22:31
add a comment |
This might just be a matter of dom load timing! There are couple of ways you can make it work.
- Adding a timer
- Using after renderer
Adding a timer
window.setTimeout(
$A.getCallback(function () {
cmp.find("itemName").focus();
}), 1
);
Renderer Approach:
afterRender: function (cmp, helper) {
this.superAfterRender();
cmp.find("itemName").focus();
}
This might just be a matter of dom load timing! There are couple of ways you can make it work.
- Adding a timer
- Using after renderer
Adding a timer
window.setTimeout(
$A.getCallback(function () {
cmp.find("itemName").focus();
}), 1
);
Renderer Approach:
afterRender: function (cmp, helper) {
this.superAfterRender();
cmp.find("itemName").focus();
}
answered Dec 20 '18 at 20:59
codeyinthecloudcodeyinthecloud
3,4451426
3,4451426
I like the Renderer approach and using it now. weird that it's not working on simple controller init. Thanks !
– sfdx bomb
Dec 20 '18 at 21:05
I agree andthis.superAfterRender();
will ensure all the default component rendering! This is something similar on Lightning data service and I usually use attribute change handlers in that case!
– codeyinthecloud
Dec 20 '18 at 21:07
+1 but instead ofafterRender
,render
is the easier and preferred approach.
– Jayant Das
Dec 20 '18 at 22:26
@JayantDas Thanks for the suggestion, the reason I went with afterRender is doc states method is called to enable you to interact with the DOM tree after the framework’s rendering service has inserted DOM elements.
– codeyinthecloud
Dec 20 '18 at 22:31
add a comment |
I like the Renderer approach and using it now. weird that it's not working on simple controller init. Thanks !
– sfdx bomb
Dec 20 '18 at 21:05
I agree andthis.superAfterRender();
will ensure all the default component rendering! This is something similar on Lightning data service and I usually use attribute change handlers in that case!
– codeyinthecloud
Dec 20 '18 at 21:07
+1 but instead ofafterRender
,render
is the easier and preferred approach.
– Jayant Das
Dec 20 '18 at 22:26
@JayantDas Thanks for the suggestion, the reason I went with afterRender is doc states method is called to enable you to interact with the DOM tree after the framework’s rendering service has inserted DOM elements.
– codeyinthecloud
Dec 20 '18 at 22:31
I like the Renderer approach and using it now. weird that it's not working on simple controller init. Thanks !
– sfdx bomb
Dec 20 '18 at 21:05
I like the Renderer approach and using it now. weird that it's not working on simple controller init. Thanks !
– sfdx bomb
Dec 20 '18 at 21:05
I agree and
this.superAfterRender();
will ensure all the default component rendering! This is something similar on Lightning data service and I usually use attribute change handlers in that case!– codeyinthecloud
Dec 20 '18 at 21:07
I agree and
this.superAfterRender();
will ensure all the default component rendering! This is something similar on Lightning data service and I usually use attribute change handlers in that case!– codeyinthecloud
Dec 20 '18 at 21:07
+1 but instead of
afterRender
, render
is the easier and preferred approach.– Jayant Das
Dec 20 '18 at 22:26
+1 but instead of
afterRender
, render
is the easier and preferred approach.– Jayant Das
Dec 20 '18 at 22:26
@JayantDas Thanks for the suggestion, the reason I went with afterRender is doc states method is called to enable you to interact with the DOM tree after the framework’s rendering service has inserted DOM elements.
– codeyinthecloud
Dec 20 '18 at 22:31
@JayantDas Thanks for the suggestion, the reason I went with afterRender is doc states method is called to enable you to interact with the DOM tree after the framework’s rendering service has inserted DOM elements.
– codeyinthecloud
Dec 20 '18 at 22:31
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.
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%2f244368%2fhow-can-i-use-lightninginput-focus-on-init%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