The text input boxes are white and when they are clicked, a blinking text cursor appears, which suggests the input is editable, even though it is currently disabled. See attached screenshot. We need to see if this is also an issue on IE6 and/or IE7.
Created attachment 422216 [details] note, despite being in view mode, the inputs are white and the first one contains a text cursor
I see the same thing on IE6 for the Inventory>Connection page. Interestingly, the boxes are properly grayed out for the Configuration sub-tabs.
I am not seeing this in IE7.0.6000
To be clear, I'm not seeing the issue in either the resource config or the conn props in IE7. Set fields are white but non-editable with no cursor. Unset fields are greyed out. Going into edit mode also works as does returning from edit mode via cancel.
Some more background on this one after some recollection... The read-only text and textarea inputs are made read-only via the readonly="readonly" attribute, rather than via the disabled="disabled" attribute. This was done, because I wanted the values to still be selectable so users could copy the values to the clipboard (this is not possible with disabled inputs). This is ok in FF, because FF grays out readonly inputs. However, it appears that IE6 and IE8 do not. So I think the solution is to figure out a way to manually gray out the inputs if on IE by changing their CSS color attributes via JavaScript. The last resort would be to use the disabled attribute instead of the readonly attribute, which would have the disadvantage of making the input values non-selectable. The following page is a helpful test page for checking how different browsers render disabled versus readonly inputs: http://tink.co.uk/disabled-read-only-form-test-page/
Further breakdown of the issue: a) Read-only resource configuration appears editable but is not. Seen in IE8(ian,charles), but not in IE7(jay,charles), IE6(joe) b) Read-only plugin configuration appears editable but is not. Seen in IE8(joe,charles), IE6(joe), but not in IE7(jay) IE Browser Versions: charles: 7.0.7530.13 Jay: 7.0.6000.16890 joseph: 6.0.2900.5512.xpsp_sp3_gdr.100216-1514 joseph: 8.0.6001.18702 charles: 8.0.7600.16385 ips: 8.0.6001.18702 Given the configuration is still not actually editable, continuing to keep this as low priority
To clarify, even FF will let you select a readonly input (which means a text cursor will appear inside the input). The difference is FF (and IE7?) will also gray out the input, while IE6 and IE8 will not. It is the selectability combined with the lack of graying out that makes the inputs really appear editable.
I need to try this out on IE8 with coregui to see if read-only properties are rendered in an intuitive fashion. We should consider just using StaticTextItems for read-only props.
Read-only props are now rendered in coregui/GWT using StaticTextItems, i.e. they will be straight text, rather than form inputs. One exception is read-only password properties, which are rendered as inputs for now due to the current lack of password property masking at the SLSB layer.
Verified on build#123 (Version: 4.1.0-SNAPSHOT Build Number: a6d2d56) Verified on Firefox3.6.3, IE7 and IE8. The read-only properties now appear as straight text. Please refer the attached screenshot taken on IE7. Marking as verified.
Created attachment 504402 [details] Screenshot
Bulk closing of old issues that are in VERIFIED state.