Ari Hyttinen commented on Bug JENKINS-9597

I just ended up disabling autocompletion on a textbox in a build step config.jelly, after having just implemented it, because I accidentally saved the job twice during testing. Considering how the job would usually not be fully configured at that point (especially since my textbox uses autoCompleteDelimChar), and considering the worst case side effects of submitting badly configured job (in my case on the level of "annoying to other people"), I find the behavior unacceptable for the end users.

Any _javascript_/jelly gurus who could provide a workaround piece of _javascript_? It would be nice, if this could be fixed in the plugin itself, for fields where it is important that reflexive enter press does not save the form? Also, having that workaround code would probably be a good first step on getting Jenkins itself "fixed", whatever that would mean in this case.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to