[MGNLUI-2930] Add Component action should be disabled for an area when maxComponents is reached Created: 20/May/14  Updated: 19/Jun/14  Resolved: 19/Jun/14

Status: Closed
Project: Magnolia UI
Component/s: actionbar, pages app, user interaction
Affects Version/s: 5.2.4
Fix Version/s: None

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Roman Kovařík
Resolution: Duplicate Votes: 0
Labels: support
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File maxComp.png    
Issue Links:
causality
duplicate
is duplicated by MGNLUI-2931 Add Component action availability 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

 Description   

If you set an area to have a maxComponents property then when that area has reached its max it should cause the "+ Add Component" action to be disabled/removed when that area has the focus.

Steps to recreate:
1. In template defs configure stkArticle base area to have a max of 2 components
2. Edit the base area of /demo-project/about/subsection-articles/article
3. Add 2 components
4. Observe the max message is showing but you still have the ability to execute the add component action.

The system still prevents the third component from being added but not until the save button is pushed in the dialog. A warning is is logged but there is no indication to the user that something has been restricted.


Generated at Mon Feb 12 09:01:33 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.