Comments on: Native JSON in Firefox 3.1

By: rdoherty

rdoherty — Tue, 04 Aug 2009 16:08:59 +0000

@Json is inSecure

Actually using native JSON or JSON.js is secure, any exploits are filtered out or ignored.

JSON is a data interchange format, not meant for people to read, so accessibility is not a concern. It’s also not for rendering pages, so being search engine friendly is not a problem.

You can compare JSON to XML or CSV files. They are for storing and transmitting data, nothing more. If accessibility and SEO become a concern when using JSON, you’re probably using it wrong.

By: Json is inSecure

Json is inSecure — Tue, 28 Jul 2009 15:48:47 +0000

Personally I hate the JSON framework, its insecure, totally goes against accessability standards, is not search engine friendly. However its always nice to have a new feature in your browser, provided that the feature wont slow down the browser and add a lot of extra crap to the code.

By: Nash Tsai

Nash Tsai — Fri, 19 Jun 2009 06:06:15 +0000

Can you do async pasring, if JSON string is going to be large, i.e., contains a large number of array elements? Will a good feature if it doesn’t exist, and to be a true ajaj

By: Timo Reitz

Timo Reitz — Thu, 30 Apr 2009 10:37:07 +0000

Patrick:

This will throw an Exception if JSON is not defined:

if (!JSON) { // Boom!
JSON = {};
}

You should do something like this:
try{
var result = JSON.parse(‘{“foo”:”bar”,”fups”:200,”xyz”:["x","y","z"]}’)
// Inspect result
}
catch(e){
// No JSON available, do it yourself
JSON=function(s){ /* … */ };
}

Or inspect this.JSON in a global context, I would recommend that.

By: sikiş izle

sikiş izle — Fri, 17 Apr 2009 22:41:03 +0000

“What’s the use of native JSON if it’s only available in Firefox? Luckily, IE8 has implemented it in RC1, which is rumored to be released in March. Hopefully other browsers will follow suit too” This part is completely misleading. IE8 has implemented Native JSON support since beta 2, which was released in August last year. saying “Hopefully other browsers will follow suit too” implies that IE8 followed Firefox 3.1, which is completely false, as in this case it’s Firefox 3.1 who followed IE8. And being intentionally vague in wording makes it sounds like IE8 will only support Native JSON sometime rumored in March this year. sikiş izle when it has already supported Native JSON for over half a year now. The correct statement should be : What’s the use of native JSON if it’s only available in Firefox? Luckily, IE8 has already implemented it in beta 2, which was released in August last year. Hopefully other browsers will follow Firefox’s step to follow suit too.

By: Joseph R. Justice

Joseph R. Justice — Fri, 17 Apr 2009 21:22:03 +0000

At this instant, for me the link at the text “new Graph Server” (http://graphs-stage2.mozilla.org/) in this blog entry goes to a page that’s basically “Hi, you’ve just installed Apache on this machine and this is the default generic home page for the installation”. I don’t know if this is specific to me, or specific to that site, but if it’s the site someone may want to fix it (or fix this link if it’s an incorrect link).

Hope this is of some use, interest. Thanks for your time.

Joseph

By: Matt

Matt — Fri, 10 Apr 2009 03:08:07 +0000

The Graph Server link takes you to a RHEL Apache test page. Did you mean to put http://graphs-stage.mozilla.org/ or did I miss something? Excellent job w/all of this btw.

By: Patrick

Patrick — Tue, 07 Apr 2009 23:11:24 +0000

You will always be allowed to use JSON.parse if available by checking if it has been defined by the browser first, just like the way you check for other features such as XMLHTTPRequest which is called something different in IE6:

if (!JSON) {
JSON = {};
}
if (!JSON.parse) {
JSON.parse = function(expr) {
eval(‘(‘+expr+’)');
}
}

By: akyaka

akyaka — Mon, 06 Apr 2009 00:36:20 +0000

So, since we’ll have to handle IE6 and IE7 for a long while, what’s the plan to use that new feature while retaining compatibility with old browsers? (Fast on modern browsers, slow but safe on old ones) Please, don’t tell me I’ll have to add one more “ and i want to say this; Apologies for the ignorant question, but what is the feasibility of doing native JSON parsing in a plug-in, sikiş , effectively allowing older versions of Mozilla to take advantage of this speed/safety improvement?

By: articles

articles — Sun, 05 Apr 2009 11:26:47 +0000

“What’s the use of native JSON if it’s only available in Firefox? Luckily, IE8 has implemented it in RC1, which is rumored to be released in March. Hopefully other browsers will follow suit too” This part is completely misleading. IE8 has implemented Native JSON support since beta 2, which was released in August last year. saying “Hopefully other browsers will follow suit too” implies that IE8 followed Firefox 3.1, which is completely false, as in this case it’s Firefox 3.1 who followed IE8. sikiş And being intentionally vague in wording makes it sounds like IE8 will only support Native JSON sometime rumored in March this year, when it has already supported Native JSON for over half a year now. The correct statement should be : What’s the use of native JSON if it’s only available in Firefox? Luckily, IE8 has already implemented it in beta 2, which was released in August last year. Hopefully other browsers will follow Firefox’s step to follow suit too.