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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you know if we need to use the property here? I see that we currently have
muted
requiring the property (node.muted = true
). Automated testing these things is tricky and I don't have a iOS10 preview to check myself - can you make a small component & run in a seed build that works, testing that toggling between true and false values when rendering actually works as expected?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm that with
HAS_BOOLEAN_VALUE
alone the property is emitted and a test page works as expected in iOS 10.I'm not sure toggling this value has a great deal of meaning though, as
playsinline
(at least as currently used by iOS) is only relevant as a modifier whenautoplay
is present. If both are true (and the video is muted or has no audio track) then iOS will play the video automatically and without fullscreen. If you toggleplaysinline
later it's unclear what we should expect -- immediate fullscreen? But re-toggling while it's fullscreen shouldn't make it go automatically inline again.I can definitely build something to test this if you'd still like to know, but any findings we get are more likely to be filed as Safari bugs than anything for react. Hopefully I didn't misunderstand the request!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@zpao
muted
is onlyMUST_USE_PROPERTY
because user interaction affects its actual value (like inputvalue
).