New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

UI Reactivity not working #2156

Closed
Torsten85 opened this Issue May 18, 2014 · 1 comment

Comments

Projects
None yet
3 participants
@Torsten85

Torsten85 commented May 18, 2014

Hey,

here is a simple repo: https://github.com/Torsten85/ui-reactivity-bug

To reproduce the error, simply click "insert" twice and then "update".
You would expect the first line to change, but this is not happening in 0.8.1.2 (in pre 0.8 releases it did).

Thanks

@glasser glasser added the Blaze label May 22, 2014

@estark37 estark37 closed this in b63328c May 27, 2014

@estark37

This comment has been minimized.

Contributor

estark37 commented May 28, 2014

Thanks for the clear repro, @Torsten85! This is fixed (+ tests) on devel.

martijnwalraven pushed a commit that referenced this issue Feb 22, 2016

Emily Stark
Add _nestInCurrentComputation flag to UI.render.
Internally, Blaze sometimes relies on `UI.render`'s autoruns nesting
within the current computation, but it's often the case that callers
don't want `UI.render`'s autoruns to be stopped when the outer
computation is invalidated. This change fixes a bug in {{#each}}: if
`addedAt` ran inside a `Deps.autorun`, and then the outer computation
was invalidated, the corresponding item would stop updating because the
autoruns set up by `UI.render` would be stopped.

Fixes #2156.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment