Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-14369

Protoype.selector undefined when using javascript proxy

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • core
    • None
    • os.arch x86_64; os.name Mac OS X; os.version10.7.4

      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='/adjuncts/493f981e/org/kohsuke/stapler/framework/prototype/prototype.js' type='text/javascript'></script><script src='/adjuncts/493f981e/org/kohsuke/stapler/bind.js' 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

            Unassigned Unassigned
            jro127 Joe Rombs
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: