Hi everyone! Our team maintains an app that was written in Aurelia 1 about 3-4 years ago. With the latest release of MacOS and Safari 26.x (Tahoe) some of the bindings have broken down completely, rendering the application unusable. This happens only in Safari - all other browsers are perfectly fine, including Chrome on MacOS.
What I’ve managed to investigate so far points to the bindings that use DirtyChecker not being tracked. We use some custom elements from our company-wide component library, and whenever the value on them gets updated, the binding does not resolve this change. It is neither reflected in the bound property in the view-model, nor does it trigger getters decorated with @computedFrom().
Registering those elements with EventManager so that the bindings trigger upon relevant change events seems to help, but given the wide scope of this problem I am unsure whether we will manage to find and fix all occurrences. My best guess at this point is that due to some changes in Safari internal workings (perhaps timings?) those dirty checked bindings are not being registered correctly and simply get lost after initial setup.
Any help, clues, or direction to look at would be greatly appreciated. Or, at this point, even the confirmation that anyone else noticed similar problems on the latest Safari would be comforting 