I used [disabled]=disabled in ion-searchbar, and it worked correctly before last update. May be it was a glitch that it worked 'cause it hasnt an attribute “disabled”.
Finally, I made new component that extends Searchbar with one new property - disabled. Realization can be taked from ion-input component. Works fine.
I think this is a bug. Searchbars do indeed have a disabled attribute, and binding to it works, in the sense that it does flip from true to false. The problem seems to be that the searchbar component itself isn’t caring.
By me it always set disabled to true independent of the value given (‘true’ or ‘false’).
But when I replaced setElementAttribute with setElementProperty and used a boolean value as a parameter, it worked in both cases, disabled (true) and enabled (false).