Yeah, looks like I steered you a bit wrong there. Technically, I don’t think it should have worked at all on the first step (because I had it set to trigger only on a step change event). Now it should work on both. I think the selector was still grabbing the input element from the first step even though it’s not showing. I tried adding the “:visible” pseudo-selector, but it did the same thing. I ended up using the “currentStep” value in the params object that’s passed through the stepchange callback. From there I was able to get at the “element” property that contains all the html elements for the step. Long story short, the code above is updated so that it should work for you (does for me).
