I've been coding for years, but I'm new to the whole open source thing so I decided that the bugsmash would be a fun way to get more involved.
About The Bug
So I went to the issue list and picked a bug that I thought would be quite straight forward based on my previous coding experience.
Embedding dev.to comment in Dev.to results in broken HTML
#4079
Describe the bug
On my post a regular dev.to comment was posted (albeit with Japanese characters in their profile) but when I embed their comment in my profile it shows broken HTML 4 tags
post (broken): https://dev.to/shushugah/gitlab-hacks-28cg comment (not broken: https://dev.to/lukeshiru/comment/e7dd
Screenshots
The bug said that embeded comments didn't work as expected, and that the html inside the comment broke.
How I Smashed It
The first step to fixing a bug is to reproduce the behavior you want to fix. So thats what I did. The "problem" was that I was not able to reproduce it. After a couple of tries, and a look at the source code my conclusion was that it was probably fixed unknowingly in an earlier release. The rendering of the html was completely different when embedding a comment today - than it was in the broken comment from the original issue.
So I added a comment to the issue, sharing my conclusion. And it was approved as a valid bug-smash. Even though I technically didn't to anything else than research. :)
Reflection
It felt almost to easy. But at the same time I feel very velcome in the community, and like the DEV team really appreciated my effort even though I didn't code anything. At least they were able to close the issue!
I will definitly see if there is another bug I can smash too!
Top comments (2)
Discovering a bug is no longer a bug is a huuuuge help! Really appreciate you working on this one and helping us close this issue. Thanks again for all your help π
Every contribution counts!! be it big or small. It's the initiative to help others that matters more βοΈ Good work π in finding the bug was no longer a bug π