Skip to content

Conversation

@inoas
Copy link

@inoas inoas commented Dec 6, 2016

Implements Issue: #442
Alternative to #586

Having a good wording of the feature also gets around default value evaluating to true instead of false. Ref: #586 (comment)

Implements Issue: w3c#442
Alternative to w3c#586

Having a good wording of the feature also gets around default value evaluating to true instead of false. Ref: w3c#586 (comment)
@inoas inoas closed this Dec 6, 2016
@frivoal
Copy link
Collaborator

frivoal commented Dec 7, 2016

This discussion is kind of spreading over a bunch of places. I made a comment in #442 (comment) to try and summaries all that's been said in terms of naming options, and try to find a winner.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants