… bleedthrough of adjacent sprites on retina displays (noticeable as pink in development mode).
…ule and pointer images at every control size. Previously, the capsule theme was only supported at SC.REGULAR_CONTROL_SIZE and the pointer theme was only supported at SC.REGULAR_CONTROL_SIZE or SC.HUGE_CONTROL_SIZE.
…ay change signature slightly
…ains a cache for String and Number GUIDs. Because the GUID for a String or a Number is essentially its own value, the caching process actually takes longer than it does to simply generate a GUID key from the given String or Number (see http://jsperf.com/cache-vs-manipulate). More importantly, this removes the memory overhead of maintaining the GUID cache, which was also unable to be cleaned. Also removed the completely unused _guidPrefixes, _numberGuids and _stringGuids objects.
…arily (doesn't require calling connect on the SC.WebSocket object to determine WebSocket support).
…lso be able to optionally check against a specific target and method. This allows the developer to properly check for the existence of a specific handler before adding it rather than only being able to check for the existence of any handler (without knowing which handler it is).
…This property is identical to the existing `parentView` property on all views. It existed in order for some ancestor view to claim ownership of a descendent view, so that the descendent could reference the ancestor directly as `owner` rather than using some chain like `parentView.parentView...`. However, this type of connection can still be achieved by the an ancestor simply assigning `owner`, or whichever property they want to use, none-the-less and there's no need for every single SC.View to have it assigned.