Automattic / Automattic/videopress-player-api-doc
Features request
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
I have two features' requests for VideoPress's JavaScript API:
1. Option to allow/restrict to certain video qualities, so that paid users can be offered higher quality videos.
Currently, to achieve this we have to upload multiple copies of the same video, one in high quality and another one in low quality.
With quality manipulation, a mobile only plan can be offered at lower price to the Sensei LMS students.
2. Option to change the video width and height after adding the video to the DOM.
videopress() method automatically handles the width and height but I found that sometimes the video does not fill the element container.
To resolve this, we can set the desirable width and height in videopress() method by passing them as options.
But once video is appended to the DOM there is no way to change the width and height without calling the videopress() method again. This is an issue especially on small screen devices where orientation change between portrait and landscape is quite common.
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
Start with the VideoPress JavaScript API and the videopress() method, focusing on how video quality options and width/height are currently handled. Review the DOM behavior after a video is appended, including orientation changes on small screens. Done means defining and implementing supported controls for quality restrictions and post-DOM dimension changes without requiring another videopress() call.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100