Commits on Feb 8, 2012
  1. Fix issue in minified build whereby models with a property called "B"…

    … would incorrectly be identified as (not) observable
    SteveSanderson committed Feb 8, 2012
  2. Rebuild

    SteveSanderson committed Feb 8, 2012
Commits on Feb 7, 2012
Commits on Feb 3, 2012
  1. Rebuild

    SteveSanderson committed Feb 3, 2012
  2. Continuation of pull request #290: Allow binding contexts to be exten…

    …ded (i.e., get a clone plus extra properties), and make them inherit custom properties from parent by default
    SteveSanderson committed Feb 3, 2012
Commits on Feb 2, 2012
  1. "isRootNodeForBindingContext" was getting very confusing because it w…

    …as being used to control decisions that were not obviously related to its name
    So, have eliminated it, and replaced it with the more specific variable "bindingContextMayDifferFromDomParentElement", which now is only used for decisions directly related to its name
    SteveSanderson committed Feb 2, 2012
  2. Extra spec to clarify need for applyBindingsToNodeAndDescendantsInter…

    …nal to bind descendant elements even if the supplied node is a comment node
    SteveSanderson committed Feb 2, 2012
  3. Force custom bindings to correctly construct child bindingContexts us…

    …ing the parent context by not exporting ko.bindingContext
    (i.e., stop custom bindings from calling "new ko.bindingContext" directly)
    SteveSanderson committed Feb 2, 2012
  4. Replace automatic inheritance of all bindingContext properties with n…

    …ew $parentContext variable
    Benefit #1: Can reach custom properties on *all* ancestor contexts, and are not limited to those that haven't been overwritten
    (e.g., if we had $index, would now be able to reach all ancestor $index values, not just the closest one)
    Benefit #2: Allows discrimination between properties at the current level and properties at the parent level, which
    is good because not all custom properties may make sense to inherit.
    SteveSanderson committed Feb 2, 2012
  5. Reverting the way binding handlers' "init" and "update" functions are…

    … invoked until the use case is clear.
    (Note that, in the future, the custom bindings API may change to become more object oriented, so each binding would
    become an object instance that can hold its own data. In case we proceed in that direction, it may be preferable
    not to be changing the "init" and "update" semantics in the meantime)
    SteveSanderson committed Feb 2, 2012
  6. Reverting the change to invokeForEachNodeOrCommentInParent (until I u…

    …nderstand what it was for)
    SteveSanderson committed Feb 2, 2012
Commits on Jan 30, 2012
  1. When building selectedValues, append to existing array instance rathe…

    …r than replacing with a new instance (just for consistency with other code in that method)
    Also make spec slightly more demanding to prove it works with multiple selections
    SteveSanderson committed Jan 30, 2012
  2. Fixing defect 300

    - Added a check for optgroup and if found it'll reuse the method passing in the optgroup
    - Added a test to validate
    aaronpowell committed Jan 30, 2012
Commits on Jan 26, 2012
Commits on Jan 25, 2012
  1. Further fix needed for #287

    SteveSanderson committed Jan 25, 2012
  2. Rebuild

    SteveSanderson committed Jan 25, 2012
Commits on Jan 23, 2012
  1. adding the other core changes from #286 :

    * Chrome sometimes appends a newline to innerText but not to textContent; so textContent is better in Chrome
    * Calling the init and update function on the object means we can use 'this' in the functions.
    mbest committed Jan 23, 2012
  2. remove allowedVirtualElementBindings export since ko.virtualElements.…

    …allowedBindings is now exported as is; remove extra space in spec test
    mbest committed Jan 23, 2012
Commits on Jan 20, 2012
  1. Export virtualElements; update bindingAttributeSyntax and templating …

    …to work with non-template virtual elements
    mbest committed Jan 20, 2012
Commits on Jan 17, 2012
  1. Harden moveNodesToContainerElement by cloning the incoming node colle…

    …ction (to ensure the contents don't change during iteration)
    SteveSanderson committed Jan 17, 2012
  2. Use div element instead of doc fragment; change 'fragment' to 'nodes'…

    …; 'text' can be set from 'nodes' but not vice versa.
    mbest committed Jan 17, 2012
  3. Setting template engines back to output DOM node arrays (even when wo…

    …rking from templates stored as document fragments) for simplicitly, as the perf appears indistinguishable
    SteveSanderson committed Jan 17, 2012
  4. For backward compatibility, revert jqueryTmplTemplateEngine to return…

    … a DOM node array instead of a docFrag.
    (Other template engines might inherit from it, and make assumptions about the result type)
    SteveSanderson committed Jan 17, 2012
  5. For backward compatibility, ensure that templateSources always supply…

    … a value for text() (where needed, by constructing and caching the value lazily based on the underlying doc frag). This also simplifes code elsewhere.
    Also renamed createAndPopulateDocumentFragment to moveNodesToDocumentFragment to emphasize that it detaches the suppled nodes from their original parent
    SteveSanderson committed Jan 17, 2012
Commits on Jan 16, 2012
  1. don't use cloneNode for IE<9

    mbest committed with SteveSanderson Jan 15, 2012