I write from time to time.
Views expressed are my own and may not represent the opinions of any entity with which I have been, am now, or will be affiliated.
Or you can write out a report by following tip #5:
A good bug report has 5 parts: A. summary B. reproduction steps C. expected result D. actual result E. current settings (ex: windows,chrome) and if you're really going for gold F. pictures/video of the problem. A report like this will make developers sing your praises to the high heavens 😇. Most issues only have a badly written part A. and it can be frustrating to even understand what's going on.
I write from time to time.
Views expressed are my own and may not represent the opinions of any entity with which I have been, am now, or will be affiliated.
That sucks! :( Unless someone reports it they won't know there's a problem to be fixed - I suggest making a issue on their github page:
github.com/thepracticaldev/dev.to/...
You can use a screen recording app to make it clear what's happening.
Or you can write out a report by following tip #5:
Maybe you can update the link to the screen recording app, because it is broken :) Thanks.
Fixed, thanks!