Fix for text not rendering after # in markdown #1033
No reviewers
Labels
No labels
android: closed alpha
android: open beta
app-parity
area: devops
area: discovery
area: docs
area: livestream
area: proposal
consider soon
creator
Epic
good first issue
hacktoberfest
help wanted
icebox
Invalid
level: 1
level: 2
level: 3
level: 4
needs: exploration
needs: grooming
needs: priority
needs: repro
needs: tech design
on hold
priority: blocker
priority: high
priority: low
priority: medium
product review
resilience
Tom's Wishlist
type: bug
type: discussion
type: improvement
type: new feature
type: refactor
type: task
type: testing
unplanned
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: LBRYCommunity/lbry-android#1033
Loading…
Reference in a new issue
No description provided.
Delete branch "md-text-rendering"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
PR Checklist
Please check all that apply to this PR using "x":
PR Type
What kind of change does this PR introduce?
Fixes
Issue Number: #960 (partial fix, do not close it)
What is the current behavior?
Due to some change introduced in Chrome, WebViews are unable to render anything after the first '#'. If that happens at the beginning of the markdown document, the HTML render will not be displayed, although the HTML code itself is correct.
Strings like '#1', '#hashtag' will make the problem appear.
What is the new behavior?
This fix changes the '#' into '%23' on the HTML generated code from markdown.
Other information
The issue indicated above was about two distincts problems. This one fixes the one from the German blog post. That file was modified, so it is no longer showing the problem. However, it was identified as being related to '#'.
The other one was about lbrycast style of claims, where video was embedded into the markdown using an IFRAME. I will also try to fix that in some future PR.
HTML generated code is correct, so in order to test it, visiting some test claims would be required. I suggest visitng following claim before and after applying the PR:
Claim to test hashtag style text
@akinwale please review/merge this
Looks good! Thanks.