Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.0.3-core, 1.0.4-core
    • Fix Version/s: 1.0.5-core
    • Component/s: Components
    • Labels:
      None
    • Environment:
      i found this issue at the trinidad version 1.0.3 and 1.0.4 - in my opinion also other versions are affected

      Description

      scenario: to show/hide input components via ppr (which are e.g. in a logical area - which is represented by a parent component -> if the area is hidden, it isn't in the dom.)
      (the rendered attribute is used here -> the parent component (of the previous mentioned parent component) has to be refreshed to show this area via ppr again)

      however, if this area is rendered and the input components of this area use client-side validation - javascript source-code gets added (dynamically) to the form.
      after hiding the area again this client-side validation source-code remains in place (until the whole form gets refreshed).
      -> if a user tries to get to the next view, the client-side validation source-code tries to validate components which aren't in the dom any more.

      workaround:
      don't use ppr for this area - trigger ppr for the complete form (i know - it's not nice to do that - it's just a workaround)

      1. Core.js.patch
        0.4 kB
        Gerhard Petracek

        Activity

          People

          • Assignee:
            Matthias Weßendorf
            Reporter:
            Gerhard Petracek
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development