You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Before you submit an issue, please complete the report with all the relevant details for your bug and go through every item in the checklist.
Describe the bug
HI i have a markdown text with more then 29.891 Characters, after that the view is blank, size of the MarkdownUI View is set correctly only the text is not shown
Checklist
[x ] I can reproduce this issue with a vanilla SwiftUI project.
[x ] I can reproduce this issue using the main branch of this package.
Steps to reproduce
Explanation of how to reproduce the incorrect behavior. This could include an attached project, a link to code, or a Markdown-formatted text exhibiting the issue.
Create a markdown with more then 29.891 Characters
run the app
Expected behavior
The expected behavior ist that the text ist shown with more then 29.891 Characters
Screenshots
The stepper is for getting the count of characters
Version information
MarkdownUI: 2.3.0
OS: iOS 17.3/17.4 and iPadOS 17.3/17.4
Xcode: 15.2
The text was updated successfully, but these errors were encountered:
Thank you for contributing to MarkdownUI!
Before you submit an issue, please complete the report with all the relevant details for your bug and go through every item in the checklist.
Describe the bug
HI i have a markdown text with more then 29.891 Characters, after that the view is blank, size of the MarkdownUI View is set correctly only the text is not shown
Checklist
main
branch of this package.Steps to reproduce
Explanation of how to reproduce the incorrect behavior. This could include an attached project, a link to code, or a Markdown-formatted text exhibiting the issue.
Expected behavior
The expected behavior ist that the text ist shown with more then 29.891 Characters
Screenshots
The stepper is for getting the count of characters
Version information
The text was updated successfully, but these errors were encountered: