This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Given how WebIDL enum work, for any one of our current strings that is an Enum, if future specs could extend them, change to DomString
25793 (for facingMode) is an instance of this problem, so adding as a dependency. Only enums that are used as function arguments (including those that are in dictionaries used as function arguments) cause this problem.
Updating to reflect that 25793 has been marked a duplicate.
VideoFacingMode has been resolved different than suggested here (with an "other" value). These leaves 2 other enums: * MediaStreamTrackState * MediaDeviceKind Both are only set by the user agent, so it's not clear to me that there would be any benefit in changing them from enums. I suggest closing as WONTFIX.
(In reply to Dominique Hazael-Massieux from comment #3) > VideoFacingMode has been resolved different than suggested here (with an > "other" value). Not that different. It's still a DOMString. The "other" enum-value just leaves the door open for Bug 19936 to let implementations use enum here in the future. > These leaves 2 other enums: > * MediaStreamTrackState > * MediaDeviceKind > > Both are only set by the user agent, so it's not clear to me that there > would be any benefit in changing them from enums. > > I suggest closing as WONTFIX. Good observation. I agree.
Closing as "WONTFIX" per Dom's and Jan-Ivar's recommendation.