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

bug with component that has an if inside an inverse tag #1115

Closed
moschel opened this Issue Jun 26, 2014 · 1 comment

Comments

Projects
None yet
2 participants
@moschel
Contributor

moschel commented Jun 26, 2014

I haven't totally narrowed this down yet, so this is mostly a placeholder so I can commit a test until I can debug further.

Here are the conditions required to reproduce this bug:

  • A component (doesn't happen with rendering a mustache template outside a component
  • That has a scope defined as an object (doesn't happen if scope is a separate viewModel can.Map)
  • That has an undefined property (doesn't happen if that property is initialized to false)
  • That has a template that has an if nested in an inverse section tag (doesn't happen without the inverse tag)
  • That later sets that undefined property to true

...Does not appear to live bind on that property correctly. Adding a breaking test

moschel added a commit that referenced this issue Jun 26, 2014

moschel added a commit that referenced this issue Jun 26, 2014

@moschel

This comment has been minimized.

Show comment
Hide comment
@moschel

moschel Jun 26, 2014

Contributor

Scratch that, the inverse tag isn't required, happens with any block tag too

Contributor

moschel commented Jun 26, 2014

Scratch that, the inverse tag isn't required, happens with any block tag too

moschel added a commit that referenced this issue May 2, 2015

@daffl daffl added this to the 2.2.6 milestone May 11, 2015

@daffl daffl added the bug label May 11, 2015

@daffl daffl closed this in #1668 May 11, 2015

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