Knockout: Disabled attribute incorrectly set

[mattLummus]

I am experiencing an issue where Knockout (3.4.2) is not consistently rendering its disable binding correctly.

We are using knockout on a single page "app" within a larger site - its a dynamic form that makes AJAX calls to update some info. We use a couple buttons to toggle state, such as a "readOnly" mode. Some buttons are disabled during certain conditions.

In this case a "Cancel" button should be disabled while any active AJAX calls are processing (which we track through a pureComputed that returns a boolean). However, while reproducing this issue, we are not actually making any edits so it should never be disabled.

To Reproduce

The Cancel button has a visible binding hooked to a readOnly pureComputed that returns a boolean. After toggling this visible binding on and off a first time, the erroneous disabled attribute pops in and remains there even though the anyProcess binding it is tied to hasn't changed...

These are the initial (and correct) !visible and visible states of this button.

(readOnly is true, button is hidden)

(readOnly is false, button is shown)

And this is how the button is rendered after toggling its visibility on/off a first time...

(readOnly is true, button is hidden but disabled)

(readOnly is false, button is shown but disabled)

I confirmed by way of logging that anyProcess does not change. I also tried letting knockout unwrap this binding in the HTML and explicitly unwrapping it myself as shown. Both had the same effect. I have tested this on Chrome, Firefox, and Safari.

[mattLummus]

There was another script that shouldn't have been included in this project that was causing a namespace conflict. Closing this issue out.

Some days you just have to talk to the duck.

[codymullins]

works on my machine! lol