27543 2014-12-09 07:34:27 +0000 Request's constructor's step to initialize "mode" needs clarification about conversion from string 2014-12-10 17:52:56 +0000 1 1 1 Unclassified WHATWG Fetch unspecified PC Windows NT RESOLVED FIXED P2 normal Unsorted 1 tyoshino annevk mike sideshowbarker+fetchspec oldest_to_newest 116038 0 tyoshino 2014-12-09 07:34:27 +0000 116039 1 tyoshino 2014-12-09 07:37:49 +0000 Allowed values for "init's mode" are strings of "same-origin", "no-cors", "cors". Allowed values for a request's associated mode are constants defined in the spec of same-origin, no CORS, CORS, and CORS-with-forced-preflight. Like the definition of the mode attribute's getter (https://fetch.spec.whatwg.org/#dom-request-mode), the constructor's algorithm should also define the conversion clearly. 116040 2 tyoshino 2014-12-09 07:40:50 +0000 BTW, is there any reason why there's no hyphen in the identifier of spec constants "no CORS" and "force cache"? Just historical? 116097 3 annevk 2014-12-10 17:49:37 +0000 https://github.com/whatwg/fetch/commit/174a674d250d9a07d61209d06bec87bc729e4c7a The reason there's no hyphen there is because no hyphen is required there in the English language, to my knowledge. Perhaps I should give up on naming internal states slightly differently from enumerations though. Or perhaps IDL should provide this mapping automatically for us (i.e. define what language to use in prose that makes it clear they are the same). 116099 4 annevk 2014-12-10 17:52:56 +0000 I filed https://www.w3.org/Bugs/Public/show_bug.cgi?id=27557 to sort out whether IDL can do something here that makes this easier for us.