Details

    • Type: Technical Testing
    • Status: Closed
    • Priority: Minor
    • Resolution: Completed
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Sprint:
      WE | Sprint 12 | Feb18 - Mar3, WE | Sprint 13 | Mar4 - Mar17
    • Test Type:

      Description

      Case 1
      Editable text elements can be edited normally as expected in a display page (rich-texts can be formatted with alloy editor if not mapped)

      Case 2
      Editable texts that are set to map to a field lose any CURRENT alloy-editor editions

      Case 3
      Editable Texts that are already mapped to a field have a limited edition of properties that can be edited and should persist through the asset actually being displayed on the display page.

      Case 4
      Unmapping a field removes any current styles applied to the editable

      Case 5
      Mapping a field should allow the "Preserve Styles" option when mapping to a field such as WC Content, which will allow the rich-text to keep its styles. This should also disable editing the styles of the editable

      Case 6
      Mapping a field and not selecting the "Preserve Styles" option for a rich-text editable should reset any style editions, but still allow the user to edit the styling

        Attachments

          Activity

            People

            Assignee:
            kyle.miho Kyle Miho
            Reporter:
            kyle.miho Kyle Miho
            Recent user:
            Marta Elicegui
            Participants of an Issue:
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:

                Packages

                Version Package