Subject: Team up to end suffering-

From: Tinnitus Prevention Bulletin <[email-masked]>
Date: Wed, 03 Dec 2014 09:20:08 -0800

Medical News Daily

Scientists Synthesize Cure for Tinnitus

Last Updated: 03 December 2014

Breakthrough Reversal System confirmed.

System to erasing Tinnitus out of your life for good has now helped cure over 105,302 people of all the frustrating ringing, hissing, buzzing.

http://www.vandtaudioservices.com/jaggy/inexactness/preparers/electrocardiograms/astrobiological/viceless.htm

No matter if your doctor or physician has told you that your tinnitus is incurable which is simply not true.

View/Edit Settings> Member RSS Feed - here

84 Marsh, Zwolle LA seven one four eight six

Tools that don't adhere to standards should be avoided whenever possible; use application/json per spec. one.beat.consumer Feb 16 '12 at 2:05
10
@one.beat.consumer while that is true, it's not specific to ExtJs per se. It's a browser limitation (or rather, perhaps, a "security measure").
4
Surely it would be better to use text/plain so it doesn't apply any HTML semantics to non-HTML content? Or don't browsers let you extract a frame's content if it's got no DOM? Synchro Aug 10 '12 at 12:34
2
"... whenever possible". Those are the magic words that change everything :) brandizzi Mar 31 '13 at 1:08

To add further confusion: I'm just debugging a similar case on Samsung Galaxy Beam (Android 2.3) with default browser, and the iframe seems to fire load event for application/javascript, application/x-javascript, text/javascript, text/plain, but NOT firing it for application/json nor text/html. As of today, Android <=2.3 is About 50% of the Android market share. a data format independent of JavaScript, and as such has its own MIME type, application/json. Respect for MIME types is of course client driven, so text/plain may do for transfer of bytes, but then you would be pushing up interpretation to the vendor application domain unnecessarily - application/json goddammit would you transfer XML via text/plain, ya big troll ya?

But honestly, assuming it's an honest question, your choice of MIME type is advice to the client as to how to interpret the data- text/plain or text/HTML (when it's not HTML) is like type erasure- it's as uninformative as making all your objects of type Object in a typed language.

No browser runtime I know of will take a JSON document and automatically make it available to the runtime as a JavaScript accessible object without intervention, but if you are working with a crippled client, that's an entirely different matter. But that's not the whole story- RESTful JSON services often don't have JavaScript runtimes, but it doesn't stop them using JSON as a viable data interchange format. If clients are that crippled... then I would consider perhaps HTML injection via an Ajax templating service instead. http://www.ata.org/