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 26087 - (object or ArrayBuffer) does not work
Summary: (object or ArrayBuffer) does not work
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: WebIDL (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Cameron McCormack
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-13 19:03 UTC by Anne
Modified: 2017-12-06 10:47 UTC (History)
3 users (show)

See Also:

Attachments

Description Anne 2014-06-13 19:03:12 UTC 
In Fetch I'm trying to make what can be returned from a stream somewhat more readable by defining an alias for JSON as object. See bug 25986.

However, that does not work as OR'ing with object causes a failure of sorts.
Comment 1 Boris Zbarsky 2014-06-13 19:05:40 UTC 
This seems similar to things like number-vs-string and whatnot.  I think we should just make 'object' distinguishable from interface types and pick the interface type if it matches.
Comment 2 Anne 2017-12-06 10:47:05 UTC 
FWIW, I no longer need this functionality (not entirely sure what changed meanwhile). I'm going to close this since it's old, but if someone considers this important please raise it over at https://github.com/heycam/webidl.