Fixed a simple logic error in record array
Fail fast with a useful error when you pass toOne or toMany an undefined value
Fixed typo in SC.Query.build method.
corrected return values for SC.Record.isError() method
Fixed Text Field Support
… the location of the browser without triggering the actual routing. Makes the use of 'statecharts' and 'routing ' much easier.
…a empty function for sparseArrayDidRequestIndexOf in the default case. This always falls back to looking locally
…targets are always on top
…otherwise it alters the styles of nested scroll views that were rendered earlier. Plus made the chained binding observe one less object, since parentView should never change for a scroller.
…after the following bug fixes) than in the default version)
SC.MenuScrollView and SC.MenuScrollerView refactor
"Change" event didn't fire on a text field preventing value from updating during focus. Changed to "keyup" event to allow live value updating without switching focus.
…ause of where Handlebars hooks into view rendering process
… the first time, rather than updating
Scroll view render delegates
…ve yet fired and that touchEnd() will come in in the same Run Loop as the one that started with the call to touchStart(). The bad thing that happens is that even though we cleared this.touch, occasionally if touchEnd() comes in right at the end of the Run Loop and then the timer expires and starts a new Run Loop to call beginTouchesInContent(), that this.touch will STILL exist here. There's no explanation for it, and it's not 100% reproducible, but there is about a 40ms window where the firing timer and the end touch cause a crash. What happens is that if we try to capture the touch that has already ended, assignTouch() in RootResponder will check touch.hasEnded and throw an exception.
…leaving a comma behind
Using multiple record types and conditions hash when calling SC.Query.build method a wrong property name was used: recordsTypes instead of recordType.
… against the root responder