Wrong context inside <content/> #2092

Closed
whitecolor opened this Issue Nov 22, 2015 · 3 comments

Comments

Projects
None yet
3 participants
@whitecolor
Contributor

whitecolor commented Nov 22, 2015

Component's template:

{{#each items}}
    <content></content>
{{/each}}

Inside content scope is not current item but component's viewModel.

@justinbmeyer

This comment has been minimized.

Show comment
Hide comment
@justinbmeyer

justinbmeyer Nov 23, 2015

Contributor

Per web-components ... only one <content> rendering makes sense. I'm not sure this sorta thing should be officially supported.

Contributor

justinbmeyer commented Nov 23, 2015

Per web-components ... only one <content> rendering makes sense. I'm not sure this sorta thing should be officially supported.

@whitecolor

This comment has been minimized.

Show comment
Hide comment
@whitecolor

whitecolor Nov 23, 2015

Contributor

Well it worked in 2.2. And multipe content tags (using select attribute) still needed feature.

Contributor

whitecolor commented Nov 23, 2015

Well it worked in 2.2. And multipe content tags (using select attribute) still needed feature.

@gsmeets

This comment has been minimized.

Show comment
Hide comment
@gsmeets

gsmeets Dec 15, 2015

Contributor

This is extremely useful, it allows you to write components like drop-down menus that can be passed (required or optional) item templates.

Contributor

gsmeets commented Dec 15, 2015

This is extremely useful, it allows you to write components like drop-down menus that can be passed (required or optional) item templates.

@daffl daffl closed this in #2139 Dec 16, 2015

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