[LIVECOPY-293] (DRAFT/VALIDATE) Reinstate "top" behaviour of LC component Created: 05/Oct/21  Updated: 14/Oct/21  Resolved: 14/Oct/21

Status: Closed
Project: Live Copy
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Laura Delnevo Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File screen-capture.webm    
Issue Links:
Relates
relates to LIVECOPY-249 Investigate: Preserve the order of co... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Epic Link: Live Copy maintenance

 Description   

TOP.  Re-instate "stick to top" behavior of Live Copies component and new push from Master BUG FIX (this behavior we fix in the past, e.g. LC-194, LC-173 and should be re-instated) 

Steps to reproduce

  1. Create a slave page and add a new component to the top of any area.
  2. Push master content changes from master
  3. The new component which was on the top is now at the bottom of the area.

.. Logs, screenshots, gifs...

Expected results

Slave page component, which is instate on the top, "stick to top" after got new push from master.

Actual results

Slave page component, which is instate on the top, "stick to top" after got new push from master.  screen-capture.webm| checked by thien.quach

Workaround

Development notes



 Comments   
Comment by Laura Delnevo [ 14/Oct/21 ]

Works as expected 

Generated at Mon Feb 12 02:27:20 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.