Brian M Hunt

Thanks @VoiceOfWisdom ... My thinking too is that there are lots of folks using error reporters like (from https://plus.google.com/+PaulIrish/posts/12BVL5exFJn): - github.com/Offbeatmammal/jsErrLog - github.com/occ/TraceKit - bugsense.com - jslogger.com - qbaka.com -...

@mbest, @rniemeyer @SteveSanderson — any thoughts on this PR?

A couple extra features: - Errors on subsequent calls to the `update` function will now be captured and passed to `ko.onBindingError` - Multiple `applyBindings` will call `ko.onBindingError` - The default...

Thank you @rniemeyer ! @mbest, @SteveSanderson - I am tagging this for 3.3 - even though I expect it would not make it in. This PR seems a fairly straightforward...

@SteveSanderson – I've been mulling it. I am guessing the easiest way to preserve the functionality would be to directly attach the metadata to the error instances. We just have...

Thanks @bjornalm Feel free to submit a similar PR to [tko.observable](https://github.com/knockout/tko.observable), and it'll make it into the next tko alpha. I think `ko.wrap` should stick to primitives, since otherwise it'd...

@simonmurdock @ehdv925 – Alas, native observables do not have a read-hook, so cannot be used for computed observables (there is no way to tell what your dependency chain is).

@simonmurdock I agree.

IIRC optgroup was broken in older IE. IMO this PR would be a good candidate for [`tko`](/knockout/tko).

Love it - thanks @saynomoo. I have not looked at it in detail, but what I have seen looks good. Cheers