Colloidal Silver Shoulder Pain

little problem with JSON

Now it appears all over the

debate between JSON and XML to me has given me a small problem that has driven me crazy because it is one of those things you do not see with the naked eye, well, I short sight.

This is when you create an array of properties:

var object = {"param1", value1, 'param2', value2, ... "ParamN" valueN
,

 Failure} clearly seen in the final   paramN a comma, when supposedly should not have. The swallows Firefox but does not create an extra element, IE swallows but also creates an extra element 

undefined. Which of the two is wrong?, Because I think both, should not accept that there was a comma (or at least that is what is stated in JSON.org
, Firefox does not create element when it encounters a comma, but it is logical to create an item, yes, do not believe that we not Javascript error. IE creates it and creates an undefined
element that has some logic, but as Firefox, not logic create a element. For this reason, that nonsense makes me go crazy looking for what a script does not behave the same in Firefox or IE.