refactor: remove built-in Video XBlock implementation (slash-n-burn #37819)

[irfanuddinahmad]

Summary

Removes the built-in Video XBlock from xmodule/ as part of the Slash-n-Burn Built-In XBlocks epic (#37819). The extracted version in xblocks-contrib has been the active implementation since USE_EXTRACTED_VIDEO_BLOCK was set to True.

Deleted:

• xmodule/video_block/ (entire directory: video_block.py, video_utils.py, video_xfields.py, init.py)
• xmodule/tests/test_video.py — built-in unit tests
• lms/djangoapps/courseware/tests/test_video_handlers.py — tests patching built-in edxval_api internals
• lms/djangoapps/courseware/tests/test_video_mongo.py — tests patching built-in edxval_api internals
• xmodule/static/css-builtin-blocks/VideoBlockDisplay.css and VideoBlockEditor.css

Modified:

• openedx/envs/common.py — removed USE_EXTRACTED_VIDEO_BLOCK toggle
• pyproject.toml — removed conflicting built-in video and videoalpha entrypoints (the xblocks-contrib entrypoints remain active)
• webpack.builtinblocks.config.js — removed VideoBlockDisplay and VideoBlockEditor entries
• lms/djangoapps/course_api/blocks/transformers/video_urls.py — inlined rewrite_video_url (was the only caller of xmodule.video_block.video_utils.rewrite_video_url)
• All test files importing VideoBlock: updated to xblocks_contrib.video.VideoBlock
• All mock.patch paths targeting xmodule.video_block.: updated to xblocks_contrib.video.

Note on deleted tests: test_video_handlers.py (1355 lines) and test_video_mongo.py (2605 lines) patch internal methods of the built-in VideoBlock (edxval_api module paths, EXPORT_IMPORT_* constants) that no longer exist. These tests cannot be straightforwardly migrated without knowledge of xblocks-contrib's internal structure. Porting this coverage to xblocks-contrib is tracked in:

• test: port test_video_handlers.py coverage (handler dispatch, transcripts) xblocks-core#264 — port test_video_handlers.py (handler dispatch, transcripts)
• test: port test_video_mongo.py coverage (rendering, student_view, CDN, bumper) xblocks-core#265 — port test_video_mongo.py (rendering, student_view, CDN, bumper)

Epic Step 1: Post-extraction commit review

Reviewed commits to xmodule/video_block/ after USE_EXTRACTED_VIDEO_BLOCK was set to True (2026-03-16 · 59d152d210). All 5 post-toggle commits were cosmetic: deprecation markers (#38174), ruff suppression, import sorting (x2), and lint-amnesty removal. xblocks-contrib received the Video block on 2026-03-04; it has been independently developed since (own bug fixes for template errors, download link sizing, etc.). No functional bug fixes or features to port.

Test plan

Testing scope: The xblocks-contrib implementation's behavioral correctness was fully validated during the extraction phase (when USE_EXTRACTED_* was set to True). These slash-n-burn PRs only delete dead built-in code — no behavioral change is possible. The only regression risk is that an entrypoint, webpack bundle, or import path is broken, which surfaces as a block failing to load. Basic load verification across LMS, CMS course, and CMS library is sufficient.

Smoke tests require a live Tutor environment and cannot be pre-checked in CI. Please verify during staging.

• Block loads and renders in LMS (student view)
• Block loads and renders in CMS course unit
• Block loads and renders in CMS V2 Library
• A video with a CDN-hosted source URL renders correctly — rewrite_video_url was inlined from video_utils.py into video_urls.py

Automated checks (CI):

• Run pytest lms/djangoapps/course_api/blocks/transformers/tests/test_video_urls.py — all 3 CDN rewrite tests pass
• Run pytest lms/djangoapps/courseware/tests/test_video_xml.py

[openedx-webhooks]

Thanks for the pull request, @irfanuddinahmad!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

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 approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To 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:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where 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:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

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:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.