In v6.0-Beta-9, the dmx-bind:disabled expressions are not being evaluated. I don’t know whether it’s a bug or my code is incorrect. All these expressions are being evaluated correctly in v5.8.2 (non-beta).
Below is an example of a dynamic disabled expression for a button element. The button should be disabled when TrialMasterCirculated==0, but it isn’t disabled when the expression is evaluated to 0 value.
Where is this button located? Is it a repeat region or inside some kind of conditional? Are you sure the TrialMasterCirculated==0 expression actually returns true, when added to your page like {{TrialMasterCirculated==0}}?
It’s in a table row that is inside a conditional div. I tested it by removing the conditional, but it doesn’t disable the button.
When I tested it by adding the expression as below on the page, it’s being evaluated correctly inside the conditional. The arrow-up icon should be disabled if TrialMasterCirculated evaulates to 0, but it stays enabled.
The updated script is evaluating the dynamic disabled expressions correctly. Thank you for this fix.
However, it is not evaluating the dynamic readonly expressions for the form input component. On one page, I had both dynamic properties - disabled buttons and readonly inputs and it’s not working for the dmx-bind:readonly input property.
I’m sorry, it was my mistake. The dmx-bind:readonly expression is being evaluated correctly. I got caught out with the same white background of the input element with readonly property, as it is for the normal input. I believe the input element with readonly property appeared with slightly darker background in previous versions.
