If a style value that ends in ; is used (i.e. color: #FF0000;) then the parser send's setStyle('colour', '#FF0000') and setStyle('', '').

The second call with a key that is empty, triggers an error in IE8 (and possibly below) when the code hits the @node.style[key] = value code below.
As I assume we should ignore blank keys, I just return false immediately.

Very difficult to test, as it works fine on all modern browsers.
Fixed a bug in IE8 where it seems that #text nodes cannot have their __acceptData property set.
A simple return of this value instead of a set seems to resolve the bug and I cannot see any instances where this will cause a problem.
The only real potential issue is a slight slowdown where calculations are required every time we query acceptData, so this may want to be made a more specific fix if desired.

Any thoughts?
Merge branch 'upstream/master'

Conflicts:
	src/view/data.coffee
Using storage key if we find it for the location for the urls when using a nested URL.

The problem was identified when using a nested hasOne. The urlNestsUnder method overwrites the url methods for the model, which in turns take priority over the _defaultCollectionUrl method inside the urlForCollection method.
The url method that is re-writted uses a plural resource name, and thus ignores the storageKey set, which (in my understanding) is what should be used.

Added backward compatibility for when storageKey doesn't exist, the legacy pluralisation is utilised.