This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
To me just using the string values throughout makes the most sense.
Yeah, I don't understand what's hard to read about using the literal string value. Seems fine to me.
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.
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.
Keep it simple :)