ICEfaces
  1. ICEfaces
  2. ICE-1113

Inconsistent rendered attribute handling on <ice:outputText>

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.5.1
    • Fix Version/s: 1.5.3
    • Component/s: ICE-Components
    • Labels:
      None
    • Environment:
      Operating System: Windows XP
      Platform: PC

      Description

      noted in the forum http://www.icefaces.org/JForum/posts/list/3182.page

      The following will show the "Always there":

      <ice:outputText rendered="false" value="Not there"><div>Always
      there</div></ice:outputText>

      The following won't show it:
      <ice:panelGroup rendered="true">
         <ice:outputText rendered="false" value="Not there">
              <div>Always there</div>
         </ice:outputText>
      </ice:panelGroup>

      So there's a couple of questions here:

      1. What is the expected behaviour on an outputText whose rendered attribute is
      false in rendering any nested tags (and would that change in a Facelets context
      where nested <div>s would be first-class components)?

      2. Why does the rendering behaviour of the outputText vary depending on its
      container (even if that container is set to rendered="true")?

        Activity

        Hide
        Adnan Durrani added a comment -

        I have tested it with the v1.5.2 and found that the problem appears with
        Facelets only. Assigning to Mark.

        Show
        Adnan Durrani added a comment - I have tested it with the v1.5.2 and found that the problem appears with Facelets only. Assigning to Mark.
        Hide
        Mark Collette added a comment -

        This might be a duplicate of IRAPtor 1276, which was fixed in 1.5.3. I have to
        investigate.

        Show
        Mark Collette added a comment - This might be a duplicate of IRAPtor 1276, which was fixed in 1.5.3. I have to investigate.
        Hide
        Mark Collette added a comment -

        Tested against 1.5.1, 1.5.2, 1.5.3, 1.6 (between drop2 and drop3).

        This was broken in 1.5.2 and before, and was fixed as of 1.5.3 (and is fixed in 1.6 as well).

        Show
        Mark Collette added a comment - Tested against 1.5.1, 1.5.2, 1.5.3, 1.6 (between drop2 and drop3). This was broken in 1.5.2 and before, and was fixed as of 1.5.3 (and is fixed in 1.6 as well).

          People

          • Assignee:
            Unassigned
            Reporter:
            Philip Breau
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: