typeahead fails if form element inside conditional block about meteor-typeahead HOT 2 CLOSED

@DanAncona as workaround try to always put typeahead input into separate template. The problem is that the package at least try to resolve data-source function from current template context and it seems it is not working in conditional blocks. Also there should be an API to pass data-source and other options explicitly to Meteor.typeahead activation function.

Also descriptive warning messages (enabled somehow only for development environment) could help to figure out with these "meteor reflection" issues.

I need to find a time to debug if there is a way to resolve functions from any meteor template context.

from meteor-typeahead.

This may actually be due to a Meteor-related bug. See below:

Fix bug where, when a helper or event handler was called from inside a custom block helper, Template.instance() returned the Template.contentBlock template instead of the actual user-defined template, making it difficult to use Template.instance() for local template state.

Source: https://github.com/meteor/meteor/blob/devel/History.md#vnext

from meteor-typeahead.