[w3c/browser-payment-api] The myth of JSON-serializable object (#307)

I might be wrong, but I recall "JSON-serializable object" coming up in the past in other specs and being problematic: 

> The term JSON-serializable object used in this specification means an object that can be serialized to a string using JSON.stringify and later deserialized back to an object using JSON.parse with no loss of data.

But I'm pretty sure it's a bit of a 🦄 - or it should be actually defined as to how one actually works that out. Right now, the spec basically implies:
```JS
try {
   JSON.parse(JSON.stringify(obj)); 
} catch(err){
   throw new Error("Not a JSON-serializable object");
}
```
 
That seems nasty. Could we check with public-script-coord what the right thing to do here is? 

There might be an actual object type that we can use here.  



-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/browser-payment-api/issues/307