27557 2014-12-10 17:52:32 +0000 Consider introducing a prose-friendly way to refer to enumerations 2016-10-22 16:41:46 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified PC All RESOLVED WORKSFORME P2 normal --- 1 annevk cam d jackalmage mike public-script-coord travil public-webapps-bugzilla oldest_to_newest 116098 0 annevk 2014-12-10 17:52:32 +0000 Context: https://www.w3.org/Bugs/Public/show_bug.cgi?id=27543 https://fetch.spec.whatwg.org/ Perhaps we should standardize on a convention on how to reference an enumeration value in a way that is not awful to read. Fetch currently maps /no CORS/ to "no-cors" but that gets somewhat verbose. On the other hand, I'd rather not use "no-cors" throughout the specification as that is harder to read. 116100 1 d 2014-12-10 17:54:54 +0000 To me just using the string values throughout makes the most sense. 116103 2 jackalmage 2014-12-10 18:50:05 +0000 Yeah, I don't understand what's hard to read about using the literal string value. Seems fine to me. 116217 3 annevk 2014-12-12 15:12:14 +0000 Once e.g. background-image and friends are defined in terms of Fetch it seems rather ugly to have prose such as Let /request/ be a new request whose mode is "no-cors" ... instead of Let /request/ be a new request whose mode is /no CORS/ ... but perhaps it is okay. 116220 4 jackalmage 2014-12-12 15:19:18 +0000 Yes, that seems totally fine to me. And will usually be much clearer, because it refers directly to the API surface in an intuitive way, rather than requiring a mapping between an abstract value and the actual enumeration that was passed in. 116246 5 travil 2014-12-13 00:42:38 +0000 Keep it simple :)