Using Valence 5.1. Appears this goes back to Extjs4, someone reported to Sencha that property did not work in beta and Sencha posted as fixed. But appears what they fixed was just setting readOnly when defining the field. If you attempt to dynamically alter that property with down('#fieldname).readOnly = true/false it does not work. Only textarea, other field types work fine.
I have yet to find a decent workaround to this on client side, if any of you have an idea please let me know. For now I'll just handle this server side, ignore updating those textareas if not in proper Valence security group.
CNX, I've not seen anyone report this to Sencha when searching web. If you could do so would carry more clout from a Gold partner than a smuck like me. Thanks!
I have yet to find a decent workaround to this on client side, if any of you have an idea please let me know. For now I'll just handle this server side, ignore updating those textareas if not in proper Valence security group.
CNX, I've not seen anyone report this to Sencha when searching web. If you could do so would carry more clout from a Gold partner than a smuck like me. Thanks!
Comment