Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-59644

Expand/collapse action for page tree child pages references an undefined HREF value.

XMLWordPrintable

      Issue Summary

      Since Confluence 7.3.1, potentially from 7+ there has been a change to the HTML markup of the page tree expand/collapse action where a HREF=undefined instead of the context path or #.

      Steps to Reproduce

      1. Create a paraent page and some children
      2. View the source code of the page
      3. Search for the word undefined.

      Expected Results

      This is an example from 6.15.7:

      <!-- 6.15.7 -->
      <div class="plugin_pagetree_childtoggle_container">
          <a id="plusminus5899375-0" class="plugin_pagetree_childtoggle aui-icon aui-icon-small aui-iconfont-chevron-down"
              href="">
          </a>
      </div>
      
      <div class="plugin_pagetree_children_content">
      
          <span class="plugin_pagetree_children_span" id="childrenspan5899375-0"> <a
                  href="/c6157/display/SQF/A?src=contextnavpagetreemode">A</a>
          </span>
      </div>
      

      Actual Results

      This is an example from 7.3.1:

          <div class="plugin_pagetree_childtoggle_container">
              <a id="plusminus1116955-0"
                  class="plugin_pagetree_childtoggle aui-icon aui-icon-small aui-iconfont-chevron-right" data-type="toggle"
                  data-page-id="1116955" data-tree-id="0" href="undefined?src=contextnavpagetreemode">
              </a>
          </div>
          <div class="plugin_pagetree_children_content">
      
      
              <span class="plugin_pagetree_children_span" id="childrenspan1116955-0"> <a
                      href="/c731/display/SQF/A?src=contextnavpagetreemode">A</a>
              </span>
          </div>
          <div id="children1116955-0" class="plugin_pagetree_children_container">
          </div>
      
      • href="undefined?src=contextnavpagetreemode" undefined is the problem

      Notes

      This can cause alerts with monitoring tools such as SiteImprove.

      From what I can tell, first href reference should be blank but we appear to be duplicating the next href, but without the context path.

      Workaround

      No known workaround. One will be provided if found in the future.

              glipatov George Lipatov
              dmark@atlassian.com Danny (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: