before changes actually happen, this way we don't have to manually dispatch the change events ourselves.
arrayContentWillChange will result in unexpected behavior in array observers.
…ntext menu or the application menu the value property was not properly updated. I tried for hours to produce a unit test to validate this change, but could not. Conflicts: frameworks/foundation/views/text_field.js
…erlay any part of the view inside the picker pane
… it is not necessary to escape numbers, older versions of this function permitted number argument and we should maintain that functionality. Especially when it is trival to do so.
…ays. Previously, SC.GridView would try to iterate through all items whenever its clippingFrame changed, triggering paging in of the entire sparse array unnecessarily. Instead it's far better to just adjust those that are nowShowing and already paged in. Also, SC.CollectionFastPath would return null if the item doesn't exist, so I made it operate like it does in SC.CollectionView to always return a view even is item is null.
SC.browser.mobileSafari returns '0' which coerces to true.
…ents on alert panes to prevent conflict. Also modified existing test to expose the current problem.