[MAGNOLIA-9156] Area Inheritance - SPA: Users can add another component when a single type area which has inherited components Created: 24/Oct/23  Updated: 30/Oct/23  Resolved: 24/Oct/23

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Anh Vu Assignee: Anh Vu
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-10-24-12-43-16-879.png    
Issue Links:
Relates
relates to MAGNOLIA-9139 Area Inheritance: maxComponents and t... Closed
relates to PAGES-1494 Area Inheritance: maxComponents and t... 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
Team: DeveloperX
Work Started:

 Description   

Currently, If an area with type:single has inherited components, users can add one more component to this area using the "Add component" button on the action bar.

Actual behavior:
A placeholder without add button on the right exist, although users cannot add components by clicking on this place holder, the can add a new components using the "Add component" button on the action bar.

Expected behavior:
The place holder should not appear and the the "Add component" button on the action bar is disabled.

Notes:

This demo project may be useful for this bug: https://git.magnolia-cms.com/projects/DOCUMENTATION/repos/component-inheritance-examples/browse


Generated at Mon Feb 12 04:39:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.