17277 2012-06-01 00:47:28 +0000 [FileAPI] It have no clear behavior about negative index of FileList.item 2012-06-01 07:38:41 +0000 1 1 1 Unclassified WebAppsWG File API unspecified PC All RESOLVED INVALID P2 normal --- 1 li.yin arun glenn jonas Ms2ger public-webapps public-webapps-bugzilla oldest_to_newest 68463 0 li.yin 2012-06-01 00:47:28 +0000 From current spec, http://www.w3.org/TR/FileAPI/#dfn-filelist MUST return the indexth File object in the FileList. If there is no indexth File object in the FileList, then this method must return null. But when the index is negative number, string, null, or undefined and so on, what should be returned, whether it should raise exception or return null directly. Currently, webkit based browser and firefox have the different behavior. 68464 1 li.yin 2012-06-01 00:53:43 +0000 According to the idl. interface FileList { getter File? item(unsigned long index); readonly attribute unsigned long length; }; unsigned long index represents the negative number is not expected. So, webkit based browser raises exception when the index is negative. 68466 2 glenn 2012-06-01 01:48:06 +0000 First, you want http://dev.w3.org/2006/webapi/FileAPI/#dfn-filelist. You almost never want "TR" links; if you find yourself on one, click the "latest editor's draft" link at the top. The behavior of unsigned long is defined by WebIDL. http://dev.w3.org/2006/webapi/WebIDL/#es-unsigned-long 68476 3 Ms2ger 2012-06-01 07:38:41 +0000 WebKit bug. Converting to an 'unsigned long' should wrap modulo 2**32.