Details

    • Epic Name:
      Rich Text Custom Tag M1

      Description

      Provide a sample dummy custom tag to be used as a basis for developers. This custom tag could be “Quote”.
      Adding the custom tag to the editor, users would get a simple window with a text area for the quote, and a field for the author, when saving, it would be previewed in the online editor.

      In scope of this milestone: block level custom tag
      Out of scope: inline level custom tag that could be used for stylig

      Suggested stories:

      • Custom tag extension point in platform UI
      • Custom tag generic interaction (create / save / edit / cancel ...)
      • Quote custom tag
      • Youtube custom tag

        Issue Links

          Issues in Epic

            Activity

            Hide
            Bertrand Dunogier added a comment -

            Moved remaining stories to custom tags M2 (EZP-28940).

            Show
            Bertrand Dunogier added a comment - Moved remaining stories to custom tags M2 ( EZP-28940 ).
            Hide
            André Rømcke added a comment - - edited

            Hi Jackson Murtha,

            yes there has been development efforts on this, however we hit a roadblock that means this feature has been postponed to later this year (eta: summer), and once we solve it we hope to deliver this feature both to 1.x (will probably serve the last 1.x release) and 2.x.

            Show
            André Rømcke added a comment - - edited Hi Jackson Murtha , yes there has been development efforts on this, however we hit a roadblock that means this feature has been postponed to later this year (eta: summer) , and once we solve it we hope to deliver this feature both to 1.x (will probably serve the last 1.x release) and 2.x.
            Hide
            Jackson Murtha added a comment -

            This issue blocks every one of my potential upgrades to Platform, including enterprise subscribers. Has any solution started development yet?

            Show
            Jackson Murtha added a comment - This issue blocks every one of my potential upgrades to Platform, including enterprise subscribers. Has any solution started development yet?
            Hide
            André Rømcke added a comment -

            > the name must contain a - (dash)

            I was mostly talking about custom tags with semantic meaning, not eztemplate generic tag.
            So we could then either map it to "ez-" or similar naming, or state custom tags must use hyphen where first part is vendor name, meaning "ez-" would be reserve for us.

            Show
            André Rømcke added a comment - > the name must contain a - (dash) I was mostly talking about custom tags with semantic meaning, not eztemplate generic tag. So we could then either map it to "ez-" or similar naming, or state custom tags must use hyphen where first part is vendor name, meaning "ez-" would be reserve for us.
            Hide
            Damien Pobel (Inactive) added a comment -

            > André Rømcke in theory (and in an ideal world ) yes we could declare the eztemplate tag as a custom element

            actually no I was re-reading various Web Components/Polymer documents lately and to be a valid custom element name, the name must contain a - (dash) so we could defined ez-template but not eztemplate.

            Show
            Damien Pobel (Inactive) added a comment - > André Rømcke in theory (and in an ideal world ) yes we could declare the eztemplate tag as a custom element actually no I was re-reading various Web Components/Polymer documents lately and to be a valid custom element name, the name must contain a - (dash) so we could defined ez-template but not eztemplate .

              People

              • Assignee:
                Unassigned
                Reporter:
                Roland Benedetti
              • Votes:
                8 Vote for this issue
                Watchers:
                17 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: