Hi again Jivan,
Here is the text I wrote in the email.
First thing I notice is that your ATMTextBoxSkin class is inheriting from ControlSkin. Was that intentional ? I think it must be a mistake, and you want it to inherit from TextBoxSkin.
Second, there seems to have been a namechange in the XSLT templates names in the framework. They changed the name, but didn‘t fix the typo J Anyway, there is a template „tplResgisterInputLostFocusEvent“ called two times in your XSLT, and the current name should be „tplResgisterLostFocusEvent“. I didn‘t check which exact version this changed in, but I am almost sure it‘s included in 6.4.0 Release b. You need to change that name.
After those two changes, there‘s no more javascript template error either obscured or not.
Third, as a general best practice rule, to support obscuring, you should name all your JavaScript functions with the control name as a prefix. I notice there are a few that are not.
For your information, the way to find things like this out is not always easy, but what I did was to create a Theme, then view the XSLT for the textbox and there I spotted the difference. Please be adviced that while the framework is evolving so rapidly, you need to expect and prepare for changes to the core XSLT, as well as other resources, and it should be a common practice when upgrading the framework to compare the resources you have overridden, or reused in a custom control, and see if there are any differences.
Hope this helps,
Palli