Bug 79291

Summary: [Chromium][V8] Support Uint8ClampedArray in postMessage
Product: WebKit Reporter: Dmitry Lomov <dslomov>
Component: WebCore Misc.Assignee: Dmitry Lomov <dslomov>
Status: RESOLVED FIXED    
Severity: Normal CC: dslomov, kbr, levin, webkit.review.bot
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Fix
none
Rebaselined none

Dmitry Lomov
Reported 2012-02-22 15:51:02 PST
Support Uint8ClampedArray in postMessage - currently they deserialzie as Uint8Arrays.
Attachments
Fix (34.83 KB, patch)
2012-02-22 18:04 PST, Dmitry Lomov 		no flags
DetailsFormatted DiffDiff
Rebaselined (34.99 KB, patch)
2012-02-22 19:34 PST, Dmitry Lomov 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Dmitry Lomov
Comment 1 2012-02-22 18:04:29 PST
Created attachment 128355 [details] Fix Can only be landed after the fix for https://bugs.webkit.org/show_bug.cgi?id=79294 lands - the latter has updated tests for Uint8ClampedArray
Dmitry Lomov
Comment 2 2012-02-22 19:20:41 PST
Comment on attachment 128355 [details] Fix Fix for 79294 landed
Dmitry Lomov
Comment 3 2012-02-22 19:34:00 PST
Created attachment 128372 [details] Rebaselined
Kenneth Russell
Comment 4 2012-02-22 19:38:56 PST
Comment on attachment 128372 [details] Rebaselined Big thumbs up. r=me Could you cq+ this yourself once it's passed the EWS bots?
Dmitry Lomov
Comment 5 2012-02-22 19:47:39 PST
(In reply to comment #4) > (From update of attachment 128372 [details]) > Big thumbs up. r=me Thumbs up not accepted. I shouldn't have missed clamped array in the test. > > Could you cq+ this yourself once it's passed the EWS bots? Sure.
WebKit Review Bot
Comment 6 2012-02-22 23:04:39 PST
Comment on attachment 128372 [details] Rebaselined Clearing flags on attachment: 128372 Committed r108613: <http://trac.webkit.org/changeset/108613>
WebKit Review Bot
Comment 7 2012-02-22 23:04:44 PST
All reviewed patches have been landed. Closing bug.
Note You need to log in before you can comment on or make changes to this bug.