Uploaded image for project: 'Magnolia UI'
  1. Magnolia UI
  2. MGNLUI-3668

MultiValueFields must react on the changes of underlying datasource

    XMLWordPrintable

Details

    • Bug
    • Resolution: Obsolete
    • Major
    • None
    • 5.4.3
    • None
    • None

    Description

      This issue is a follow-up of the fix/improvement done in the scope of MGNLUI-3633. The situation is far from ideal - even though the underlying datasource does not get overridden as a consequence of the fields not being in synch with the model, the fields still don't get updated if the underlying data changes.

      Vaadin's ValueChangeEvents should be sent in appropriate situations and fields, especially MultiFields must react on such changes and update their state/UI.

      For the future assignee:
      One should delete the workarounds (markAsDirty() calls) which were introduced with MGNLUI-3844.
      If this ticket solves the root problem, those shouldn't be needed anymore.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                Unassigned Unassigned
                apchelintcev Aleksandr Pchelintcev
                Votes:
                5 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD