Skip to content
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

Wrapped in an if-clause and bound regex pattern is modified and if-clause property is toggled #169

Open
notmessenger opened this issue Sep 13, 2016 · 0 comments

Comments

@notmessenger
Copy link
Member

The resolution of #161 introduced this bug. When {{ef-element-error}} is not wrapped in an {{#if}} all works as expected. When it is wrapped in an {{#if}} and

  • If condition is initially false, not displaying this component
  • The if condition is toggled to true
  • The bound error pattern of this component is changed to one that still matches.
  • The bound error pattern of this component is changed to one that does not match.
  • The default instance of this component will display its content because there are no pattern matches in any of the other instances.

but

  • If condition is initially false, not displaying this component
  • The if condition is toggled to true
  • The bound error pattern of this component is changed to one that still matches.
  • The if condition is toggled to false
  • The if condition is toggled to true
  • The bound error pattern of this component is changed to one that does not match.
  • The default instance of this component will NOT display its content even though it should because there are no pattern matches in any of the other instances.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant