New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ReactWebChat] Markdown Base64 Images not getting rendered #1896
Labels
bug
Indicates an unexpected problem or an unintended behavior.
front-burner
p0
Must Fix. Release-blocker
Projects
Comments
corinagum
added
bug
Indicates an unexpected problem or an unintended behavior.
Triage-E
labels
Apr 15, 2019
@denscollo, thanks for filing this issue! If you have the time to do a PR with the fix, please feel free to do so! We appreciate your help. |
Investigate for 4.4 |
corinagum
added
the
backlog
Out of scope for the current iteration but it will be evaluated in a future release.
label
Apr 16, 2019
corinagum
added
4.5
front-burner
and removed
backlog
Out of scope for the current iteration but it will be evaluated in a future release.
needs-repro
Waiting for repro or investigation
labels
May 7, 2019
@denscollo, could you tell me what format the data uri was in? synk and the markdown-it security page indicate that only pngs, gifs, and jpgs are allowed in |
Hi @corinagum, sorry for the delay. We were using pngs for our tests. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Indicates an unexpected problem or an unintended behavior.
front-burner
p0
Must Fix. Release-blocker
Version
v4.3.0
Describe the bug
Marked down base64 encoded images not getting rendered. Instead shows the image caption.
We tested it on Azure Portal and HTML Sites (using also the example) and it works perfectly. When trying this approach on a React-App, using ReactWebChat, the images are not getting rendered.
Screenshots
Bot with Markdown Base64 image on Azure Portal Web Chat
Bot with MarkdownBase64 Image using ReactWebChat (on Chrome and Mozilla Firefox)
The text was updated successfully, but these errors were encountered: