Fix incorrect firing of NEW_CONTENT_ADDED in TabManager.js

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Type: Bug
    • Resolution: Won't Fix
    • Priority: High
    • None
    • Affects Version/s: 5.1
    • Component/s: None
    • 5.01

      NEW_CONTENT_ADDED is being fired incorrectly in TabManager.js. It is being fired twice on the same context - the tab container - rather than the elements that the are inside the tab container.

      For QA: this affects the following pages:

      • Manage filters (/secure/ManageFilters.jspa)
      • Manage dashboards (/secure/ConfigurePortalPages!default.jspa)
      • User profile (/secure/ViewProfile.jspa)

              Assignee:
              Jonathon Creenaune
              Reporter:
              Jonathon Creenaune
              Archiver:
              Michael Andreacchio

                Created:
                Updated:
                Resolved:
                Archived: