Skip to content

Key filter breaks when VM has components #247

Closed
@seanami

Description

@seanami

This is a really weird bug that I ran into, but I've boiled it down to a simple test case and it really does seem to be a legit bug. When a VM has the components property set, any key filters used in directives in the component template or root template cease to function properly.

Simple test case: http://jsfiddle.net/smcbride/5fN4c/

You'll notice that when you run the example, you should see console logging when you hit enter in both text fields. However, no console lines are logged. If you delete the div v-component from the template and the components property from the VM definition and re-run the example, then a single text input is rendered and console lines are logged when you hit enter.

That seems totally crazy! How could the presence of components in the root VM stop all key filters from working? This drove me nuts for over an hour. Wacky.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions