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

can-value="." not working properly #800

Closed
ghost opened this Issue Mar 19, 2014 · 8 comments

Comments

Projects
None yet
4 participants
@ghost

ghost commented Mar 19, 2014

When binding the current context to an input element via can-value="." changing its value shows following exception in firebug:

TypeError: rootObserve is undefined

http://jsfiddle.net/J4Q5M/1/

@daffl

This comment has been minimized.

Show comment
Hide comment
@daffl

daffl Mar 19, 2014

Contributor

What browser? The Fiddle works without errors in Firefox and Chrome for me.

Contributor

daffl commented Mar 19, 2014

What browser? The Fiddle works without errors in Firefox and Chrome for me.

@matthewp

This comment has been minimized.

Show comment
Hide comment
@matthewp

matthewp Mar 19, 2014

Contributor

@daffl modify one of the inputs and the click away (blur).

Contributor

matthewp commented Mar 19, 2014

@daffl modify one of the inputs and the click away (blur).

@daffl

This comment has been minimized.

Show comment
Hide comment
@daffl

daffl Mar 19, 2014

Contributor

Ah got it. For me it says can not read property isComputed of undefined.

Contributor

daffl commented Mar 19, 2014

Ah got it. For me it says can not read property isComputed of undefined.

@matthewp

This comment has been minimized.

Show comment
Hide comment
@matthewp

matthewp Mar 19, 2014

Contributor

The problem is here. .read is only returning a value, not the other properties.

Contributor

matthewp commented Mar 19, 2014

The problem is here. .read is only returning a value, not the other properties.

@Zemljoradnik

This comment has been minimized.

Show comment
Hide comment
@Zemljoradnik

Zemljoradnik Dec 4, 2014

I have the same issue, it's not limited to can-value=".".
For example: http://jsfiddle.net/s9fp54nu/ and http://jsfiddle.net/5geohr7w/

Is there a workaround, or is can-value to be avoided?

Zemljoradnik commented Dec 4, 2014

I have the same issue, it's not limited to can-value=".".
For example: http://jsfiddle.net/s9fp54nu/ and http://jsfiddle.net/5geohr7w/

Is there a workaround, or is can-value to be avoided?

@DVSoftware

This comment has been minimized.

Show comment
Hide comment
@DVSoftware

DVSoftware Dec 4, 2014

Contributor

@Zemljoradnik it works like this: http://jsfiddle.net/s9fp54nu/1/
In order to use 2 way binding, you need to use Maps

Contributor

DVSoftware commented Dec 4, 2014

@Zemljoradnik it works like this: http://jsfiddle.net/s9fp54nu/1/
In order to use 2 way binding, you need to use Maps

@Zemljoradnik

This comment has been minimized.

Show comment
Hide comment
@Zemljoradnik

Zemljoradnik Dec 4, 2014

@DVSoftware Thanks, I get it now.

Zemljoradnik commented Dec 4, 2014

@DVSoftware Thanks, I get it now.

@daffl

This comment has been minimized.

Show comment
Hide comment
@daffl

daffl Oct 22, 2015

Contributor

This is fixed in 2.3.0.

Contributor

daffl commented Oct 22, 2015

This is fixed in 2.3.0.

@daffl daffl closed this Oct 22, 2015

@daffl daffl added this to the 2.3.0 milestone Oct 22, 2015

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