Use attributes instead of properties (compatibility with elm-safe-virtual-dom)
#598
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Intro
This is a companion PR to elm/virtual-dom#187 and elm/html#259 from Simon Lydell's lydell/elm-safe-virtual-dom.
🎗️ This PR should be merged if and only if elm/html#259 is merged. Meaning this should not be merged before that PR is merged, but it needs to be merged when that PR is merged.
Changes here mirror changes made by Simon Lydell to
elm/htmlin elm/html#259:stringPropertyhelper functionvalueboolPropertyand documents its behavior under the new Virtual DOMelm-cssalready mirroredelm/html, and this keeps that aspect of it tidy =]Impact of not merging
If Simon's PRs are merged,
avh4/elm-program-testtests will fail unless we also merge this PR.An example failure can be seen in this gist, where we fail to find a select option based on the
forattribute of the select's label.The cause is
elm-program-testbuilds its selectors directly withelm/html'sHtml.Attributes.In the example above,
elm-csswill build anhtmlForproperty for our view, andelm/htmlunderelm-safe-virtual-domwill build aforattribute forelm-program-test's selector.Details
Quoting Simon: