Revert "fix: Preserve fullscreen mode for embedded content in WebView"

[PruthiviRaj27]

Reverts #818

Summary by CodeRabbit

• Refactor
  • Streamlined the video embedding process for a more consistent viewing experience.
  • Removed third-party cookie handling for embedded content, which may change interactions with external services.

[coderabbitai]

Walkthrough

The changes remove the third-party cookie acceptance feature from the WebView in the video fragment. The HTML generation logic for video embedding has been simplified by eliminating conditional checks based on the presence of a "fullscreenContent" class. The code now consistently constructs the HTML wrapper for video embeds without differentiating based on the embed content. No modifications were made to any public or exported entities.

Changes

Files Changed	Change Summary
course/src/main/java/in/testpress/course/fragments/WebViewVideoFragment.kt	Removed the third-party cookie acceptance code and simplified the conditional HTML construction logic by directly building the HTML wrapper for video embeds.

Sequence Diagram(s)

sequenceDiagram
    participant U as User
    participant VF as WebViewVideoFragment
    participant WH as WebView
    U->>VF: Request to play video
    VF->>VF: Construct HTML wrapper for video embed (simplified)
    VF->>WH: Load generated HTML
    WH-->>U: Render video content

Loading

Poem

In the realm of code so bright,
I hopped and skipped through day and night,
Cookies gone, HTML refined,
A simpler path we now have signed.
With a twitch of my nose and a heart so light,
I celebrate these changes in pure delight!
🐰💻✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d1ca474 and a02b77d.

📒 Files selected for processing (1)

• course/src/main/java/in/testpress/course/fragments/WebViewVideoFragment.kt (1 hunks)

🔇 Additional comments (1)

course/src/main/java/in/testpress/course/fragments/WebViewVideoFragment.kt (1)

88-89: HTML generation for video embed has been simplified, potentially affecting fullscreen behavior.

The code now uses a simpler approach to wrap the video embed code without conditional checks for "fullscreenContent" class. Since this is a revert of a previous fix for preserving fullscreen mode, please verify that:

1. This simplification doesn't negatively impact fullscreen functionality, especially for different types of embedded content
2. The original issues that led to PR fix: Preserve fullscreen mode for embedded content in WebView #818 won't resurface with this change
3. Fullscreen behavior works correctly on both orientation changes and when using the fullscreen controls within videos

Could you clarify why the previous fix needed to be reverted? Was there an issue with the conditional approach that checked for "fullscreenContent"?

✨ Finishing Touches

• 📝 Generate Docstrings

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai plan to trigger planning for file edits and PR creation.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.