-
New Feature
-
Resolution: Fixed
-
Major
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
HL & LD 12, HL & LD 13, HL & LD 14, HL & LD 15, HL & LD 16, HL & LD 17
-
13
Timebox for investigation:
- How to pass the data/annotations? Does not necessarily have to REST
—
There are many new tickets being created that relate to the html annotations in the page that are then used by the page editor. A part of resolving those tickets will involve changing the frontend-helpers library to change the annotation code to add some aspect that is present in the original server-side annotation creattion code.
In the development of the Visual SPA Editor feature there was a choice to be made about how the annotations should be added with the frontend helpers. It was decided to re-implement the annotation creation in the frontend helpers, rather then to retrieve the annotations from the server.
Based on these new tickets, and the realization that new modules (live copy, abtesting, etc) can impact the annotations, we should reassess that decision and see if there is a better approach such that we won't have to continuously change the frontend helpers library to accomodate new features being added to Magnolia on an ongoing basis.
Please see linked "caused by" tickets to see issues that might be related to this topic.
- caused by
-
MGNLFE-67 React helper ignoring area title
- Closed
-
MGNLFE-65 SPA Editor: Magnolia area dialog is displayed even though "editable:false" is set
- Closed
-
MGNLFE-66 SPA Editor: Areas in Magnolia show a dialog for components even if there are no components in this area available
- Closed
-
MGNLFE-68 I18n Labels for area / component titles do not work
- Closed
-
MGNLFE-70 Frontend-helpers should support editable and deletable attribute
- Closed
-
MGNLFE-64 Personalization variants not supportined with front end libs
- Closed
-
MGNLFE-57 Allow more control on the HTML Comment generation
- Closed
-
MGNLFE-58 Allow using dialog at area level
- Closed
-
MGNLFE-61 Support for user-defined area templates
- Closed
-
MGNLFE-62 EditableArea is rendering a mgnlEditorBar at noComponent Area
- Closed
- is causing
-
PAGES-356 DOC: New template-annotations endpoint
- Closed
- is depended upon by
-
MGNLFE-77 Update React & Angular Editors to use new endpoints
- Closed
- is related to
-
MGNLFE-74 Property maxComponents is not taken into account in the area definition
- Closed