• We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      jQuery is our standard JS library in Confluence now, so we need to rewrite functionality to use it instead of Prototype.

      This seems to be a little bit more important now because some functionality isn't working properly with jQuery 1.3 because of Prototype's overriding of document.getElementByClassName().

            [CONFSERVER-16441] Replace usages of Prototype.js with jQuery

            I reviewed this.

            m@ (Inactive) added a comment - I reviewed this.

            Agnes Ro added a comment -

            Labels javascript has been rewritten to use jquery now and Prototype/Scriptaculous libraries are no longer present on Confluence pages.

            A legacy web resource plugin has been written (disabled by default) for customers to easily enable in case a plugin is still dependent on these libraries.

            Agnes Ro added a comment - Labels javascript has been rewritten to use jquery now and Prototype/Scriptaculous libraries are no longer present on Confluence pages. A legacy web resource plugin has been written (disabled by default) for customers to easily enable in case a plugin is still dependent on these libraries.

            Agnes Ro added a comment -

            With CONF-16571, the page permissions javascript was rewritten so that the only dependency on Prototype/Scriptaculous is now labels.

            I guess this issue can now just be called, rewrite labels javascript so it doesn't rely on DWR or Prototype.

            Agnes Ro added a comment - With CONF-16571, the page permissions javascript was rewritten so that the only dependency on Prototype/Scriptaculous is now labels. I guess this issue can now just be called, rewrite labels javascript so it doesn't rely on DWR or Prototype.

            Turns out that the most difficult part of this is the labels auto-complete drop-down. It has a copy of some Scriptaculous autocomplete control, modified for our use.

            I think the easiest way would be to rewrite the autocomplete to reuse our jQuery dropdown code, like found in the search screen user picker.

            Matt Ryall added a comment - Turns out that the most difficult part of this is the labels auto-complete drop-down. It has a copy of some Scriptaculous autocomplete control, modified for our use. I think the easiest way would be to rewrite the autocomplete to reuse our jQuery dropdown code, like found in the search screen user picker.

              agnes@atlassian.com Agnes Ro
              matt@atlassian.com Matt Ryall
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: