You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can I ask what the reason is for having a focus call in the clear placeholder function? I'll describe my problem below:
In IE8 (maybe earlier browsers, but haven't checked), the control would fire a partial postback after a button click. This would cause the form delegate to fire, which in turn caused the clear placeholder function to fire on each of the inputs. Inside this method, it focusses each password field. The result being (since the last password field is below the fold) that the scroll position is changes when the field gains focus, so that it's within the field of view. I therefore did two things which fixed it for me:
Commented out the focussing code - "$input.focus();"
Fired the placeholder plugin on a partial postback of the page using Sys.WebForms.PageRequestManager.getInstance().add_endRequest(FunctionToInitialisePlaceholders);
Is the focussing required, because it seems to have caused me issues with unintentional page scrolling on a partial postback.
The text was updated successfully, but these errors were encountered:
Hi there,
Can I ask what the reason is for having a focus call in the clear placeholder function? I'll describe my problem below:
In IE8 (maybe earlier browsers, but haven't checked), the control would fire a partial postback after a button click. This would cause the form delegate to fire, which in turn caused the clear placeholder function to fire on each of the inputs. Inside this method, it focusses each password field. The result being (since the last password field is below the fold) that the scroll position is changes when the field gains focus, so that it's within the field of view. I therefore did two things which fixed it for me:
Is the focussing required, because it seems to have caused me issues with unintentional page scrolling on a partial postback.
The text was updated successfully, but these errors were encountered: