Opened 13 years ago

Closed 13 years ago

Last modified 12 years ago

#1011 closed defect (fixed)

Support application/json in dojo.io transports

Reported by: guest Owned by: James Burke
Priority: high Milestone:
Component: Core Version: 0.2
Keywords: Cc:
Blocked By: Blocking:

Description

According to the draft RFC, the preferred mime type for JSON is "application/json", but all of the transports in dojo.io only accept "text/json".

As a kind of aside, it took me a while to dig up this issue. I now understand that what I should do is inspect the request object returned by dojo.io.bind for its "bindSuccess" value, but that idiom isn't easy to find in dojo docs. (It doesn't show up at all in the "baking usability" document.) If nothing else, perhaps it would help to add a dojo.debug("No transports can handle your request") in io.js before returning.

Change History (4)

comment:1 Changed 13 years ago by dylan

Milestone: 0.4
Owner: changed from anonymous to alex

alex, any preference on what to do with this one?

comment:2 Changed 13 years ago by dylan

Owner: changed from alex to James Burke

comment:3 Changed 13 years ago by James Burke

Resolution: fixed
Status: newclosed

(In [6181]) Fixes #1011, support application/json. Also fixed IframeIO.js canHandle: the stricter checking I did in dojo.io.bind() caused IframeTransport? binds to fail unless they had a file upload field. Since we are going to allow using url: with IframeTransport? (references #1170) I removed the file input requirement for IframeTransport?.

comment:4 Changed 12 years ago by (none)

Milestone: 0.4

Milestone 0.4 deleted

Note: See TracTickets for help on using tickets.