[JIRA] (JENKINS-14369) Protoype.selector undefined when using javascript proxy

[joero...@yahoo.com (JIRA)]

Joe Rombs created JENKINS-14369 Protoype.selector undefined when using _javascript_ proxy Issue Type: Bug Affects Versions: current Assignee: Unassigned Components: core Created: 10/Jul/12 1:01 AM Description: The problem seems to be that the When I create a job for the first time in which the config.jelly file contains an <st:bind> tag a Prototype.js script is included which overrides the expected version of Prototype.js. More specifically the problem shows up when I use an <f:repeatable> tag along with using an <st:bind> tag for a _javascript_ proxy. If I don’t include the bind tag in my config.jelly and then look at the script tab of firefox firebug I see that the version of Prototype.js included is 1.7. If I put the st:bind tag back in, I get two prototype.js files, version 1.7 as well as 1.6.0.2. Looking at firebugs console the following call POST http://localhost/8080/$stapler/bound/4491b11f-e8f7-46a8.../render The response contains the following in place of the bind tag <script src='' type='text/_javascript_'></script><script src='' type='text/_javascript_'></script><script>agilityProxy=makeStaplerProxy('/$stapler/bound/2792d54d-45c9-4cc0-a122-964b9cbc2309','80a20c17-7ae1-46f7-bf37-be40579c1bc8',['getProjects','getArtifacts','getSolutions']);</script> which contains the inclusion of the differing prototype.js Environment: os.arch x86_64; os.name Mac OS X; os.version10.7.4 Project: Jenkins Priority: Major Reporter: Joe Rombs

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