As I understand it payments wants to say the data you're sending needs to be serializable to send over the wire to a payment system. SerializedScriptValue is structured clone, which doesn't define a wire format and instead is just an algorithm to serialize/deserialize. ex. This thing shouldn't allow message ports, array buffers, dates, regexes, etc.
On Thu, Mar 31, 2016 at 3:09 PM, Jochen Eisinger <[email protected]> wrote: > Do you plan to support the additional parameters (replacer and gap)? > Anyways, feel free to send the CL to me and verwaest@. > > Out of curiosity, why this odd definition of an object that can be > serialized and deserialized instead of the standardized > SerializedScriptValue IDL type? > > On Thu, Mar 31, 2016 at 11:40 PM Rouslan Solomakhin <[email protected]> > wrote: > >> Hi, >> >> I am planning to expose JSON::Stringify API to Blink, similar to how >> JSON::Parse was exposed in https://codereview.chromium.org/21959003/. I >> am following the instructions at >> https://github.com/v8/v8/wiki/Contributing. This is for >> http://crbug.com/587995. Who would be a good code reviewer for this >> patch? >> >> Cheers, >> Rouslan >> >> -- >> -- >> v8-dev mailing list >> [email protected] >> http://groups.google.com/group/v8-dev >> --- >> You received this message because you are subscribed to the Google Groups >> "v8-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > -- -- v8-dev mailing list [email protected] http://groups.google.com/group/v8-dev --- You received this message because you are subscribed to the Google Groups "v8-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
