Bug 145976 - [Streams API] Calling controller.error() should trigger storing an undefined error
Summary: [Streams API] Calling controller.error() should trigger storing an undefined ...
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: youenn fablet
URL:
Keywords:
Depends on: 145839
Blocks:
  Show dependency tree / graph
 
Reported: 2015-06-15 09:19 PDT by youenn fablet
Modified: 2015-06-16 10:36 PDT (History)
4 users (show)

See Also:

Attachments
Patch (7.43 KB, patch)
2015-06-15 23:56 PDT, youenn fablet 		no flags Details | Formatted Diff | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description youenn fablet 2015-06-15 09:19:25 PDT 
Currently, when error() has no parameter, we create a default error.
We should just store a jsUndefined() value.
Comment 1 youenn fablet 2015-06-15 23:56:08 PDT 
Created attachment 254940 [details]
Patch
Comment 2 WebKit Commit Bot 2015-06-16 10:36:48 PDT 
Comment on attachment 254940 [details]
Patch

Clearing flags on attachment: 254940

Committed r185592: <http://trac.webkit.org/changeset/185592>
Comment 3 WebKit Commit Bot 2015-06-16 10:36:53 PDT 
All reviewed patches have been landed.  Closing bug.