triniwiz / triniwiz/nativescript-plugins
'playsInLine' is problematic on iOS and unavailable on Android
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 87
- Forks
- 57
- Avg merge
- 1h 36m
- Merged PRs (30d)
- 4
Description
The Good
With playsInLine="true" on iOS, my app waits until player is ready, then allows user to tap to play. A black, fullscreen view opens and video plays.
Problem 1: no auto-close and multiple taps required
If I allow it to play through then view remains until user closes it. User must tap once to show controls, then tap [X] to close. App knows when when video plays to end (EOF) but there is no API call to close the view.
Problem 2: black screen, double-close
If user taps to show controls and then taps [X] during playback, video appears to animate away but black/empty view remains until user taps [X] again.
Problem 3: inconsistent re-play behavior
If user toggles view by closing and re-playing, every other 'play' will re-start playback where it left off, but on every other 'play' video will be paused (playback does not continue). App is also limited because it doesn't know when view closes.
Problem 4: documentation
'playsInLine' is marked (checked) for Android in the doc here...
https://triniwiz.github.io/nativescript-plugins/api-reference/youtube-player.html#api
...but the underlying feature is not supported on Android...
https://developers.google.com/youtube/player_parameters#playsinline
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the linked youtube-player API reference and Google playsinline parameter documentation first. Reproduce the listed iOS close and replay behavior, verify the Android support discrepancy, and consider the work complete when the reported behavior is addressed or the unsupported behavior is documented accurately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, ios
- Domain
- mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100