Skip to content

Check for valid json serializer fails if there is no window.json #2003

Closed
NTaylorMullen opened this Issue May 8, 2013 · 1 comment

2 participants

@NTaylorMullen

The fix is to check if there's a valid json serializer at the connection construction level rather than checking window.json on load.

@NTaylorMullen NTaylorMullen was assigned May 8, 2013
@NTaylorMullen NTaylorMullen added a commit that referenced this issue May 8, 2013
@NTaylorMullen NTaylorMullen Moved logic to check for valid json serializer to be in .start
- Minified/compiled auto gen'd files

#2003
68dc05c
@NTaylorMullen NTaylorMullen added a commit that referenced this issue May 8, 2013
@NTaylorMullen NTaylorMullen Moved logic to check for valid json serializer to be in .start
- Minified/compiled auto gen'd files

#2003
612c960
@NTaylorMullen NTaylorMullen added a commit that referenced this issue May 13, 2013
@NTaylorMullen NTaylorMullen Moved logic to check for valid json serializer to be in .start
- Minified/compiled auto gen'd files

#2003
ca5a646
@NTaylorMullen NTaylorMullen added a commit that referenced this issue May 13, 2013
@NTaylorMullen NTaylorMullen Moved logic to check for valid json serializer to be in .start
- Minified/compiled auto gen'd files

#2003
c53eeee
@Xiaohongt Xiaohongt was assigned May 13, 2013
@Xiaohongt
SignalR member

verified

@Xiaohongt Xiaohongt closed this May 16, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.