Bug 32384 – MultiInput plus button hides if already clicked and max constraint changes

Bug 32384 - MultiInput plus button hides if already clicked and max constraint changes


Summary:	MultiInput plus button hides if already clicked and max constraint changes

Status:	RESOLVED DUPLICATE of bug 42597

Product:	UCS
Classification:	Unclassified
Component:	UMC (Generic)
Version:	UCS 3.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UMC maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2013-08-27 10:20 CEST by Florian Best
Modified:	2016-10-07 17:29 CEST (History)
CC List:	1 user (show)

See Also:
What kind of report is it?:	---
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Florian Best

2013-08-27 10:20:22 CEST

require('umc/dialog').alert((m = new umc.widgets.MultiInput({ subtypes: [{name: 'foo', type: 'TextBox'}]})))

m.set('max', 1)
→ clicking on plus [+] correctly hides the [+] button
m.set('max', 4)
→ the [+] button is hidden and can not be reached anymore

This bug occurs in the system setup when adding network interfaces after changing the interface type.

Comment 1 Alexander Kläser

2013-08-27 15:30:24 CEST

If this is a blocker for the network page, we will fix it. My guess would be that the problem does not occur in other places as the max value is not dynamically used.

Comment 2 Florian Best

2015-06-09 13:01:32 CEST

I had trouble with this again. I implemented a fix in a subclass in UDM which should be moved into the main class.

Comment 3 Florian Best

2016-10-07 17:29:00 CEST


*** This bug has been marked as a duplicate of bug 42597 ***