Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Leaking (the new) if binding introduced in v1.5.2 #328
I'm submitting a bug report
Please tell us about your environment:
A leaking if binding behind nested if binding
Run the test app, just click next and next, all conditional DOM are not removed.
Pretty sure this is introduced by #324 which attempt to fix another issue on the new if/else implementation.
This issue doesn't exist on v1.5.1 before #324 fix.
bring back old if.bind please...
The new if/else implementation changed too much, created lots of new edge cases (just read through your issue list). The result is breaking everybody's production app. I have to say this is not a production ready feature.
Please please revert back to old if binding implementation. And put this new implementation into a beta/preview release for people to try.
I suggest to maintain a conservative Aurelia stable release, and only test experimental features on beta/preview release.
I am back to v1.4.0 again.