Ba/issue 3 #21849
Open
Ba/issue 3 #21849
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…droid into ba/issue-3
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The issue, described in #21171, involved a bug where inserting a YouTube video via URL in the video block resulted in the raw link being displayed instead of an embedded, playable video in the preview. This occurred because the app relied on plain HTML and did not process the URL properly for embedding.
To fix this, we modified the
WordPress/src/main/java/org/wordpress/android/ui/WPWebViewActivity.javafile to wrap the provided video URL in an<iframe>element, ensuring it is recognized and rendered as an actual embedded video during preview.Testing instructions
closes #21171