Bug 1093025 - [RFE] Add an infrastructural mechanism for differentiation between user and programmatic selection
Summary: [RFE] Add an infrastructural mechanism for differentiation between user and p...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: RFEs
Version: ---
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
: ---
Assignee: bugs@ovirt.org
QA Contact: Pavel Stehlik
URL:
Whiteboard:
Depends On:
Blocks: 1069269 1167087
TreeView+ depends on / blocked
 
Reported: 2014-04-30 12:46 UTC by Daniel Erez
Modified: 2019-04-28 10:02 UTC (History)
7 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-05-16 11:40:50 UTC
oVirt Team: UX
Embargoed:
ylavi: ovirt-future?
ylavi: planning_ack?
ylavi: devel_ack?
ylavi: testing_ack?


Attachments (Terms of Use)

Description Daniel Erez 2014-04-30 12:46:49 UTC
Description of problem:
As discussed in bug 1069269, in the described scenario, a selection of list-box item by the user should be preserved (i.e. shouldn't be overridden by a programmatic selection). For that, a means for identifying whether the selection has been originated from the user is needed (in order to treat it respectively). Once introducing such mechanism, it should probably be generalized to support any type of widget.

Additional info:
Further details regarding the issue in bug 1069269.

Comment 1 Itamar Heim 2015-03-29 09:06:35 UTC
Closing old bugs. If this issue is still relevant/important in current version, please re-open the bug.

Comment 2 Allon Mureinik 2015-03-29 10:43:04 UTC
This RFE is required to (properly) solve bug 1069269.

I'm reopening it for reconsideration, since afaik the closure on comment 1 was an automatic script, not a thought process that specifically decided this RFE can't/shouldn't be fixed.

Comment 3 Greg Sheremeta 2018-05-16 11:40:50 UTC
We are attempting to move away from GWT in webadmin and switching to micro-frontend architecture with react plugins implementing pieces of the UI.

Therefore, we'll avoid writing GWT code as much as possible, and certainly can't prioritize any GWT infrastructure.


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