Bug 88534

Summary: [Chromium] Move WebSerializedScriptValue to Platform/chromium/public/
Product: WebKit Reporter: Mark Pilgrim (Google) <pilgrim>
Component: WebKit Misc.Assignee: Mark Pilgrim (Google) <pilgrim>
Status: RESOLVED WONTFIX    
Severity: Normal CC: abarth, dglazkov, fishd, haraken, jamesr, tkent+wkapi, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Bug Depends on:    
Bug Blocks: 82948    
Attachments:
Description Flags
Patch none

Mark Pilgrim (Google)
Reported 2012-06-07 07:02:37 PDT
[Chromium] Move WebSerializedScriptValue to Platform/chromium/public/
Attachments
Patch (16.00 KB, patch)
2012-06-07 07:03 PDT, Mark Pilgrim (Google) 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Mark Pilgrim (Google)
Comment 1 2012-06-07 07:03:39 PDT
Created attachment 146281 [details] Patch
WebKit Review Bot
Comment 2 2012-06-07 07:07:45 PDT
Please wait for approval from abarth@webkit.org, dglazkov@chromium.org, fishd@chromium.org, jamesr@chromium.org or tkent@chromium.org before submitting, as this patch contains changes to the Chromium public API. See also https://trac.webkit.org/wiki/ChromiumWebKitAPI.
Adam Barth
Comment 3 2012-06-07 16:12:43 PDT
Comment on attachment 146281 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=146281&action=review > Source/Platform/ChangeLog:8 > + Part of a refactoring series. See tracking bug 82948. Is there a specific reason for moving this interface? It's not clear to me whether it should be in the Platform part of the API.
Adam Barth
Comment 4 2012-06-07 16:15:41 PDT
I see. It's related to IDB.
Eric Seidel (no email)
Comment 5 2012-10-08 16:12:06 PDT
Comment on attachment 146281 [details] Patch Cleared review? from attachment 146281 [details] so that this bug does not appear in http://webkit.org/pending-review. If you would like this patch reviewed, please attach it to a new bug (or re-open this bug before marking it for review again).
Note You need to log in before you can comment on or make changes to this bug.