-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
textarea input type not working for IE9 #54
Comments
I'll have a patch release out later today. I did hit this issue in other IE versions and must have forgot to test in IE9 again. Doh! |
@TronixGT I just tested this in IE6-10 and it's working on properly on each one. Are you able to provide me with a link so I can see it in action? |
I don't yet have an example. Our site is intranet, but let me see if I can put together a demo. |
I can't seem to figure out whats happening. If I make a stand-alone form it works but I can't get it to work inside of an asp.net app. Even if I strip everything down and just use a plain form with nothing but the jquery framework and the autotab it will not work. You can only type one letter and then it freezes in the textarea. Regardless if you set a maxlength or not. I'm going to keep poking around with it. My workaround for the moment will be to invoke the .remove for textarea's but I'll keep trying to figure out what's going on with it. |
Odd. Instead of calling |
Good call, I ended up doing that. The .remove wasn't working. I've narrowed down the issue.. It has something to do with Compatibility Mode in IE. I'm currently upgrading our site to be HTML5/CSS3 compliant, but we still have an older code base on the interface that requires the users to run in compatibility mode. I've begun transitioning all of our forms and at the top of each new form that uses jQuery 1.9 and Autotab 1.7 I include a: "meta http-equiv="X-UA-Compatible" content="IE=edge" tag to force IE out of compatibility mode. It works right for 10, but not for 8 or 9. I can deal with not initializing textarea's for now, since there are only maybe 8 of them out of our 800+ fields. Once I get everything upgraded and take everyone out of compatibility mode, I don't think this will be an issue. I don't suppose there is a way to initialize a field and apply a filter to it, but not the tab feature? |
You could call this, but the |
I just installed 1.7 and it appears that the new maxlength update is not compatible with IE9 (at least). I've tested it in IE10 and it works, but with IE9 you cant type anything in a textarea (with or without a maxlength set). I'm going to continue fiddle with it and see if I can figure out whats causing it.
The text was updated successfully, but these errors were encountered: