Right now, dropzones don't have any type of ID and fragments added to multiple dropzones are rendered in the different dropzones in the order they are defined.
This makes that, when dropzones are reordered (or new dropzones are placed in between), already existing fragments inside these dropzones are not kept in the original dropzone they were added to
- Allow fragment developers to add IDs to dropzones with data-lfr-drop-zone-id
- Fragments added to dropzones will keep the relationship with that given dropzone, so that if the dropzone changes, fragments inside will be kept.
- It will be mandatory that all dropzones inside a custom fragment have IDs. If there is one dropzone without ID, the fragment editor will return an error letting the user know that all dropzones must have ID.
- Dropzone ID is NOT mandatory. If there is no ID, they will behave as the previous dropzones
Dropzone IDs must be unique for a given page. Document this limitation for developers to be aware of this.
|Test Scenarios||Test Strategy||Kind of test||Is it covered by FrontEnd ? (JS-Unit)||Is it covered by BackEnd ? (unit or integration)||Could it be covered by POSHI?|
|Fragments inside dropzones will be kept by data-lfr-drop-zone-id when new drop zone is added||CRITICAL||Manual||No||Yes||Yes|
|Fragments inside dropzones will be kept by data-lfr-drop-zone-id when drop zone is removed||CRITICAL||Manual||No||Yes||Yes|
|Fragments inside dropzones will be kept by data-lfr-drop-zone-id when drop zone position is switched||CRITICAL||Manual||No||Yes||Yes|
|Can not add dropzone inside a custom fragment with duplicate data-lfr-drop-zone-id||MEDIUM||Manual||No||Yes||Yes|
|If using data-lfr-drop-zone-id in one dropzone inside a custom fragment, then all the dropzones inside a custom fragment should have data-lfr-drop-zone-id||MEDIUM||Manual||No||Yes||Yes|
|Can add dropzone inside a custom fragment without data-lfr-drop-zone-id||MEDIUM||Manual||No||Yes||Yes|
|Fragments inside dropzones will be kept by data-lfr-drop-zone-id when new drop zone is added in staging||MEDIUM||Manual||No||No||Yes|
To take into account when documenting this story:
When a dropzone with an id is deleted and propagated, that dropzone and its content will be removed from the page. Putting a dropzone with the same id back in the fragment will only be able to retrieve the content of the dropzone in those drafts that have not been published after the first propagation. In those that have been published, the dropzone will be considered a new dropzone.
LRDOCS-11378 Docu: As a Fragment Developer I want to keep fragments related to the dropzones they were added to
- is related to
LPS-171311 LPS-167932 - Product QA | Test Automation Creation
- mentioned in