Timeline for Why does Visualforce inputField using html-disabled = false still disable the field?
Current License: CC BY-SA 4.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 1, 2019 at 2:14 | vote | accept | Irene | ||
| Jul 1, 2019 at 1:35 | comment | added | Charles T | Glad to hear. I added the comment to my answer. | |
| Jul 1, 2019 at 1:35 | history | edited | Charles T | CC BY-SA 4.0 |
added 289 characters in body
|
| Jun 30, 2019 at 22:20 | comment | added | Irene | I have done that - solved my problem. | |
| Jun 30, 2019 at 3:40 | comment | added | Charles T |
I suppose you could put two consecutive instances of <apex:inputField>, one disabled with rendered="{! !allowChoice}" and the other enabled with rendered="{!allowChoice}". That way VF will only ever render one of them at a time. Or make the read-only one an <apex:outputField>.
|
|
| Jun 30, 2019 at 1:20 | comment | added | Irene | So how do I achieve what I'm trying to do then if I can't use this - do you have an alternative suggestion maybe please? | |
| Jun 28, 2019 at 11:55 | history | answered | Charles T | CC BY-SA 4.0 |