Uploaded image for project: 'Magnolia pages module'
  1. Magnolia pages module
  2. PAGES-500

Component always shows original - even if you select a different variant. Handling component variant selection states on client side

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Neutral
    • 6.2.12
    • 6.2.11
    • None

    Description

      Currently variant states be synchronized w/ server-side via cookie, sent along w/ the template-annotations/definitions request. Will not work with separate origins & third-party cookies ban

      • Start managing page-editor state on the client side (SPA/standalone page-editor), e.g. like scroll position
      • intercept variant selection event before we communicate to the outer frame via postmessage?

      If keeping state using browser's sessionStorage, selection is lost when browser tab is closed. This is expected and acceptable. Alternatively localStorage may be more persistent.

      Checklists

        Acceptance criteria

        Attachments

          Issue Links

            Activity

              People

                jsimak Jaroslav Simak
                lam.nguyen Lam Nguyen Bao
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Checklists

                    Bug DoR
                    Task DoD

                    Time Tracking

                      Estimated:
                      Original Estimate - Not Specified
                      Not Specified
                      Remaining:
                      Remaining Estimate - 0d
                      0d
                      Logged:
                      Time Spent - 5h
                      5h