fastfasterfastest
fastfasterfastest
Isn't the problem that ko.contextFor does _not_ return a context?
I was merely trying to clarify the issue the OP is reporting - OP reported that `ko.contextFor` returns a context with no `$root` property; I think the issue the OP...
Obviously the behavior is different in 3.5.0 vs. what it was in 3.4.2. And to be strictly backward compatible the behavior should not change. But it can be argued that...
And you agree it is a bug? We surely can't have - `with: expr` - `foreach: expr` - `template: { data: expr }` behave differently when it comes to how...
A workaround to avoid the error in the distilled sample is to wrap the `foreach` with a reference to `phrases`: ``` ``` In my live app that is not sufficient,...
Related, if not identical, to https://github.com/knockout/knockout/issues/2285 I agree w/ https://github.com/knockout/knockout/issues/2285#issuecomment-333520124 in that issue - a function value should not be called "to unwrap it". If the value is an observable...
I'd disagree that it has "worked" since 3.0 - I'd agree that it perhaps has "worked like this" since 3.0. Two stranges don't make it not strange, though. I think...
And I am not sure the behavior has been stable since 3.0. E.g., here is a list of behavioral changes of `with` binding due to a recent commit https://github.com/knockout/knockout/commit/b67e42f5ca896885e6313f5821f64d99d02efd19 (although...
> it doesn't make 100% clear that the latency is due to Knockout and Knockout only I would even venture to say that it is likely not due to knockout...
Just addressing this comment: > Make a small modification to KO, just before the throw error; line (in the example above). Log the error parameter of debugError to the console....