ICEfaces
  1. ICEfaces
  2. ICE-7373

NotificationPanel: Switching between tabs causes another notificationPanel div to be rendered

          Details

          • Type: Bug Bug
          • Status: Closed
          • Priority: Major Major
          • Resolution: Won't Fix
          • Affects Version/s: 2.1-Beta
          • Fix Version/s: 3.0
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            Test application be used is located at: repo\qa\trunk\Regression-Icefaces2\Sparkle\Nightly\notificationPanel
            ice & ace tabSet
          • Workaround Exists:
            Yes
          • Workaround Description:
            Hide
            Put the notificationPanel outside the rendering/unrendering container component, and just put it within the body anyways, since that's where it'll end up getting rendered regardless. Or inside a form but outside the containers that start and stop rendering it.
            Show
            Put the notificationPanel outside the rendering/unrendering container component, and just put it within the body anyways, since that's where it'll end up getting rendered regardless. Or inside a form but outside the containers that start and stop rendering it.

            Description

            To reproduce:
            1. Load test application
            2. Navigate to one of the tabSet tests (either Sparkle or Panel)
            3. Switch tabs back and forth
            Notice that a new div is being created each time you return to the tab with the notificationPanel.

            Screenshot 1: This is the initial page load.
            Screenshot 2: This is after switching to 'Tab 2' and back to 'Tab 1'.
            Screenshot 3: This is after switching to 'Tab 2' and back to 'Tab 1' again.
            1. 1.png
              127 kB
            2. 2.png
              127 kB
            3. 3.png
              127 kB

              Activity

              Ascending order - Click to sort in descending order
              Cruz Miraback created issue -
              Cruz Miraback made changes -
              Field Original Value New Value
              Attachment 1.png [ 13687 ]
              Attachment 2.png [ 13688 ]
              Attachment 3.png [ 13689 ]
              Ken Fyten made changes -
              Salesforce Case []
              Assignee Priority P2
              Assignee Mark Collette [ mark.collette ]
              Mark Collette made changes -
              Workaround Description Put the notificationPanel outside the rendering/unrendering container component, and just put it within the body anyways, since that's where it'll end up getting rendered regardless. Or inside a form but outside the containers that start and stop rendering it.
              Workaround Exists [Yes]
              Salesforce Case []
              Ken Fyten made changes -
              Status Open [ 1 ] Closed [ 6 ]
              Assignee Priority P2
              Resolution Won't Fix [ 2 ]

                People

                • Assignee:
                  Mark Collette
                  Reporter:
                  Cruz Miraback
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: