Repository navigation
Conversation
- Add audio_tracks field to VideoFields in video_xfields.py - Expose audioTracks in block.py metadata - Implement 08_video_audio_track_control.js supporting HLS audio groups (Path A) and source-swap (Path B) - Register VideoAudioTrackControl in 10_main.js - Add player CSS for audio track menu in video.css - Add multilingual video how-to guide to documentation Generated with the assistance of Antigravity (Google DeepMind). Co-authored-by: Antigravity <[email protected]>
…language-preference cookie and improve dropdown styling - Style audio track dropdown with button.audio-option to match LMS theme - Inspect `openedx-language-preference` cookie on initialization and automatically align the default transcript/subtitle and audio track languages when the learner changes their platform language preference, while preserving individual overrides made on the player controls. Generated with assistance from Antigravity. Co-authored-by: Antigravity <[email protected]>
… and language sync Expand docs/how-tos/multilingual_videos.rst to detail: - Spoken audio track configuration via Studio Basic tab (HLS and MP4 with #lang= fragments / filename suffixes) and Course OLX. - Subtitle and transcript configuration (CC and interactive transcript panel). - Automatic synchronization with the learner's `openedx-language-preference` cookie while preserving manual in-player overrides. Generated with assistance from Antigravity. Co-authored-by: Antigravity <[email protected]>
|
Thanks for the pull request, @mboisson! This repository is currently maintained by Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review. 🔘 Get product approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:
🔘 Submit a signed contributor agreement (CLA)
If you've signed an agreement in the past, you may need to re-sign. Once you've signed the CLA, please allow 1 business day for it to be processed. 🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. DetailsWhere can I find more information?If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources: When can I expect my changes to be merged?Our goal is to get community contributions seen and reviewed as efficiently as possible. However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
|
Hi @mboisson! Welcome, and thank you for this contribution! In order for your CLA check to turn green, you'll need to submit a CLA form. If you are contributing as an individual, please fill out the individual CLA form here. If you are contributing on behalf of an organization, please have your manager reach out to [email protected] so you may be added to your org's existing entity agreement. Please let me know if you have any questions. Thanks! |
Merge checklist:
Check off if complete or not applicable: