Bug 790179

Summary:	config editor: member maps of list-o-maps will be made read-only if the member map prop def is read-only
Product:	[Other] RHQ Project	Reporter:	Ian Springer <ian.springer>
Component:	Core UI	Assignee:	Nobody <nobody>
Status:	NEW ---	QA Contact:
Severity:	high	Docs Contact:
Priority:	medium
Version:	4.2	CC:	hrupp
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ian Springer 2012-02-13 20:41:26 UTC

This is wrong, because there are a couple special cases where we allow the user to edit member props even if the corresponding member prop def is read-only, namely:

// special case 1: property has a plugin-set error message - allow user to edit it even if it's a read-only prop,
// otherwise the user will have no way to give the property a new value and thereby get things to a valid state
// special case 2: required simple prop with no value - allow user to edit it even if it's a read-only prop,
// otherwise the user will have no way to give the property a new value and thereby get things to a valid state

So to implement this correctly, we would need to check whether each member map is read-only one by one, rather than just checking if the prop def is read-only.

Comment 1 Mike Foley 2012-02-27 17:13:10 UTC

triage 2/27/2012 mfoley, asantos, crouch, loleary