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
"Preview" does not work when replying to a comment #20681
Comments
Thanks for the issue, we will take it into consideration! Our team of engineers is busy working on many types of features, please give us time to get back to you. To our amazing contributors: issues labeled If this is a feature request from an external contributor (not core team at Forem), please close the issue and re-post via GitHub Discussions. To claim an issue to work on, please leave a comment. If you've claimed the issue and need help, please ping @forem-team. The OSS Community Manager or the engineers on OSS rotation will follow up. For full info on how to contribute, please check out our contributors guide. |
@GwartneyDev no, it's not like that - in this case you can't even get to the preview in the first place. It looks like the library used for previewing things isn't loaded unless you have a post to edit already (speculation). |
@moopet Ah ok that is weird, will have to see if I can test it on my side at some point. Just figured I would ask in general since the other one just seemed similar. |
I'm unable to replicate the issue, has it been solved? |
Just following up to see if this was ever solved? |
This is still a problem, and I still see "handleCommentPreview is not defined" in the console in Chrome and Firefox. |
This seems to be similar to #20389, @joaoGabriel55 opened an PR to solve it! #20394 |
Describe the bug
The "preview" button does not work when replying to a comment.
In the console we see:
To Reproduce
Expected behavior
We see some sort of preview of the markdown, either in-place or as a separate interstitial page.
Screenshots
Desktop (please complete the following information):
Additional context
This is a continuation of #19290 which was closed with only a partial fix last year.
The text was updated successfully, but these errors were encountered: