[CONTEDIT-221] Initial block showing duplicated controls Created: 31/Jan/20  Updated: 18/Aug/21  Resolved: 27/Jul/21

Status: Closed
Project: Content Editor
Component/s: None
Affects Version/s: 1.3.3, 1.3.4
Fix Version/s: 1.3.9

Type: Bug Priority: Neutral
Reporter: Jonathan Ayala Assignee: Oanh Thai Hoang
Resolution: Fixed Votes: 4
Labels: VN-Analysis, VN-Implementation, VN-Testing, maintenance
Remaining Estimate: Not Specified
Time Spent: 1d 0.5h
Original Estimate: Not Specified

Attachments: PNG File Screenshot 2020-01-31 at 13.49.57.png    
Issue Links:
causality
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[X]* Steps to reproduce, expected, and actual results filled
[X]* Affected version filled
Date of First Response:
Epic Link: Stories App maintenance
Sprint: Content Mngmt 09
Story Points: 5

 Description   

When initialBlock block property is set to other than text, move up/down, remove and add controls are shown twice and they don't work when user clicks on them. However, by switching the view to another tab and coming back immediately, duplicity disappears and everything works as expected.

Steps to reproduce in our demo:

  1. Modify /stories-app/apps/stories.yaml to change initialBlock property from text to image (line 586)
  2. Go to stories app and create a new story: controls appears twice and don't work
  3. Switch tab (without closing the new story one) to main and come back to the new story tab: controls appear and work correctly


 Comments   
Comment by Annick Boehler [ 13/Oct/20 ]

Hi there,

FYI: I got the same issue reported from SwissRe (on Magnolia 6.2.3) 
Is there any timeline when this issue will be fixed?

Thanks 

Comment by Matthias Jakob [ 22/Feb/21 ]

Any progress here?

Comment by Annick Boehler [ 04/Mar/21 ]

Still reproducible in 6.2.6. 

May I ask if there are any updates? 

Thanks

Comment by Oanh Thai Hoang [ 23/Jul/21 ]

Hi all, CM team is working on this bug in this sprint CM-09

Comment by Oanh Thai Hoang [ 27/Jul/21 ]

Provided the PR fixed for 1.3.9 only, version 2.0 can't not reproduce this bug

Generated at Mon Feb 12 00:18:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.