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 17892 - WD-FileAPI-20120712 has a dynamic attribute FileReader#result
Summary: WD-FileAPI-20120712 has a dynamic attribute FileReader#result
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 07:13 UTC by contributor
Modified: 2012-08-26 00:43 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-07-18 07:13:22 UTC 
This was was cloned from bug 17776 as part of operation convergence.
Originally filed: 2012-07-14 03:38:00 +0000
Original reporter: Fuji Goro (gfx) <g.psy.va+w3org@gmail.com>

================================================================================
 #0   Fuji Goro (gfx)                                 2012-07-14 03:38:39 +0000 
--------------------------------------------------------------------------------
As you see in http://www.w3.org/TR/2012/WD-FileAPI-20120712/,

interface FileReader: EventTarget {
  readonly attribute (DOMString or ArrayBuffer)? result;
};

The "result" attribute is a union type defined in WebIDL.
This IDL might be valid, but how do statically-typed languages like Java represent it?

I think HTML specs should not use union member types because there are webidl-to-statically-typed-language-definition tools.

Regards,
---------
gfx
================================================================================
Comment 1 Ian 'Hixie' Hickson 2012-08-24 19:02:42 UTC 
JavaScript is the main target.
Comment 2 Fuji Goro (gfx) 2012-08-26 00:43:59 UTC 
Thanks for the answer.