Bug 42597 – make MultiInput a complete widget

Bug 42597 - make MultiInput a complete widget


Summary:	make MultiInput a complete widget

Status:	REOPENED

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

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

URL:
Keywords:

Duplicates:	24015 24489 27770 28992 31779 32384 33016 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-10-07 13:00 CEST by Florian Best
Modified:	2019-02-06 11:25 CET (History)
CC List:	4 users (show)

See Also:	30110
What kind of report is it?:	Development Internal
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

2016-10-07 13:00:15 CEST

MultiInput has no reset() method. Therefore code like:

173 »   »   restart: function() {
174 »   »   »   tools.forIn(this.getPage('item')._form._widgets, function(iname, iwidget) {
175 »   »   »   »   if (iname === 'password') {
176 »   »   »   »   »   iwidget._setValueAttr(null);
177 »   »   »   »   } else if (iname !== 'school_classes') {
178 »   »   »   »   »   iwidget.reset();
179 »   »   »   »   }
180 »   »   »   });

fails when a MultiInput was added to a form.

Comment 1 Florian Best

2016-10-07 17:28:50 CEST

There are a lot of bug reports against MultiInput:

* Bug #42597
→ missing function reset()

* Bug #33016 - add validator function for MultiInput widgets
→ missing evaluation of function validator()

* Bug #32384 - MultiInput plus button hides if already clicked and max constraint changes
→ fix available in UDM subclass

* Bug #28992 - MultiInput should return list of objects
→ A new widget for a list of objects would be nice and handy

* Bug #24489 - MultiInput: remove duplicated values from selection
→ In UDM all values are set()s. The GUI should be able to handle this.

* Bug #24015 - Dependencies inside MultiInput
→ The subtypes of MultiInput can't have dependencies. Especially complex-syntax types are broken due to this.

Comment 2 Florian Best

2016-10-07 17:28:56 CEST

*** Bug 33016 has been marked as a duplicate of this bug. ***

Comment 3 Florian Best

2016-10-07 17:29:00 CEST

*** Bug 32384 has been marked as a duplicate of this bug. ***

Comment 4 Florian Best

2016-10-07 17:29:04 CEST

*** Bug 28992 has been marked as a duplicate of this bug. ***

Comment 5 Florian Best

2016-10-07 17:29:08 CEST

*** Bug 24489 has been marked as a duplicate of this bug. ***

Comment 6 Florian Best

2016-10-07 17:29:13 CEST

*** Bug 24015 has been marked as a duplicate of this bug. ***

Comment 7 Florian Best

2016-10-07 18:13:26 CEST

Missing methods focus() and validate()
→ Bug #30110

Comment 8 Florian Best

2016-10-10 13:37:51 CEST

* [+] and [-] buttons still work if the widget is disabled
→ Bug #31779

Comment 9 Florian Best

2016-10-10 13:38:00 CEST

*** Bug 31779 has been marked as a duplicate of this bug. ***

Comment 10 Florian Best

2016-10-10 16:15:25 CEST

*** Bug 27770 has been marked as a duplicate of this bug. ***

Comment 11 Florian Best

2016-10-10 16:16:26 CEST

Bug #27770 - Mehrere identische Dienste führen zu einer unschönen Fehlermeldung
→ In UDM all values are set()s. The GUI should be able to handle this.
→ Same as Bug #24489

Comment 12 Stefan Gohmann

2019-01-03 07:19:38 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.