This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 13165 - How should result be serialized?
Summary: How should result be serialized?
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML Microdata (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-06 21:27 UTC by contributor
Modified: 2011-08-04 05:05 UTC (History)
5 users (show)

See Also:


Attachments

Description contributor 2011-07-06 21:27:40 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html
Multipage: http://www.whatwg.org/C#json
Complete: http://www.whatwg.org/c#json

Comment:
How should result be serialized?

Posted from: 81.234.240.242
User agent: Opera/9.80 (X11; Linux x86_64; U; Edition Next; en) Presto/2.9.168 Version/11.50
Comment 1 Philip Jägenstedt 2011-07-06 21:33:21 UTC
Step 5 says "Return the result of serializing result to JSON." but doesn't define how to serialize it. I suggest referencing JSON.stringify from [ECMA262] section 15.12.3 with no replacer or space parameter given, such that it is exactly equivalent to calling JSON.stringify(result).
Comment 2 Ian 'Hixie' Hickson 2011-07-07 23:05:36 UTC
Doesn't JSON define how to serialise something to JSON?
Comment 3 Ian 'Hixie' Hickson 2011-07-08 00:17:50 UTC
I guess JSON does leave some things undefined.

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.

(I didn't refer to JS because it's not a JS object we're serialising here, so it's an extra unnecessary layer of abstraction.)
Comment 4 contributor 2011-07-08 00:18:01 UTC
Checked in as WHATWG revision r6284.
Check-in comment: Define how to serialise JSON for use in drag-and-drop.
http://html5.org/tools/web-apps-tracker?from=6283&to=6284
Comment 5 Michael[tm] Smith 2011-08-04 05:05:23 UTC
mass-move component to LC1