Prevents exception when using borderFrame property with useStaticLayout views before they have rendered.  Includes updated unit tests.
Fixes problem with optimization to layoutDidChange that failed to resize children if the layout lacked width & height defined.  Updates unit tests.
Fixes typo in comment.
Fixes typo in test name.
Adds the concept of Infinity to SC.IndexSet.  Although, the number of indexes will always be constrained to Number.MAX_SIZE, attempting to create a range even in the several hundreds of thousands would freeze the client, because it will attempt to generate hints every 256 items.  Instead we can use the concept of infinity and don't try to hint the infinite range.  For one, this allows for infinite arrays and infinite lists to be possible without using really large numbers that are very slow to hint.

Includes unit tests.
Fixes typo in documentation.
Fix inline text field position

Since this commit:
https://github.com/sproutcore/sproutcore/commit/4d199900fcd8a60f757c10a8
2de01b5f0576a907 (which were welcome since besides fixing the z-index,
it also fix a problem where if an inline text field was in a scroll
view, the field wasn't moving when scrolling), the calculation of
position of the editor was completely wrong. This can be see in the
showcase, with the SC.LabelView and the SC.ListView examples.
Based on my app and the showcase app, this commit fix the problem. I
haven't added units test because I believe this can't be tested.
Note that I've also dropped IE7 support for this since I'm not able to
test it and because even Twitter Bootstrap will drop IE7 support in
there next release.
Fix review

Review of the positionOverTargetView method after dcporter report.
Removed blurOnMouseDown which is not needed anymore.
Add support for the multiline flag.
Forget to remove some obsolete code
Deprecates the unused arguments in SC.InlineTextField:positionOverTargetView.
Fixes unit tests to pass for previous change to inline text field.
Improves and fixes the platform animation test.  Previous version was just plain not smart, new version uses a style element within the test element.  Which means that we don't have to worry about having a stylesheet to modify or having to search through the stylesheet for clean up.  Instead, the style element is scoped to the test element and when we toss out the test element it takes care of all clean up.
Fix SC.LabelView inline editing

If an SC.LabelView is inside a collection view the doubleClick method
can't be call because the collection will handle the mouseDown event.
Uses the doubleClick event handler rather than mouseUp since the conditional already exists in root responder.
Updates deprecated attr() in attributeBindings internal code.  Fixes #933
Fixes regression with label view that accepted mouseDown on double click even if it was not editable (prevented the double click from bubbling).
Fixes SC.Cursor's determination of its internal stylesheet object.  Previously, it would just take the last stylesheet, but any style elements in the body would match this.  Instead we find the stylesheet whose node matches the element we insert for the cursor object.

Includes unit test.
Updates SC.RecordArray's pacing code to use the updated invokeNext function instead of setTimeout.
Fixes a problem with pooling views.  If the layerId changed, the original layerId was unknown and the original cache of the view in SC.View.views would not get removed.
There was an issue that if you destroyed a child view, it would destroy its
layer and remove itself from the parent, which in turn invoked updateLayerLocationIfNeeded
in parentViewDidChange.  If before updateLayerLocationIfNeeded ran a new
child was created with the same layer id, when updateLayerLocationIfNeeded
did run it would remove the new layer from the parent.

The solution was that if a view is destroyed, don't invoke updateLayerLocationIfNeeded.

- includes unit test