https://bugs.documentfoundation.org/show_bug.cgi?id=168918
--- Comment #6 from Buovjaga <[email protected]> --- (In reply to Danat from comment #5) > (In reply to Buovjaga from comment #4) > > (In reply to Danat from comment #3) > > > (In reply to fpy from comment #2) > > > > Please be more specific in filling in the form and attaching relevant > > > > files > > > > here. > > > > > > > > see https://wiki.documentfoundation.org/QA/BugReport#Good_reports > > > > > > Respectfully, there seems to be no way to file a bug in a way that would > > > satisfy you. There is always something you don't like about it > > > > > > Who do you think you are? I made a video and gave you the file. Is that > > > not > > > enough? > > > > > > I gave you the video to watch and the file in case you might need it > > > > A video can provide an additional look at an issue, but you should describe > > enumerated steps to reproduce the problem. > > I gave those steps in other reports, and he still didn't approve them. In my > opinion, those steps can sometimes create more confusion than understanding > > If I read the steps, most of the times, I will have no clue about the issue. > But if somebody showed me - that would give me much more understanding. > Spoken language is not good at conveying software bugs I've triaged something like 15 thousand reports here and elsewhere and I disagree. Written steps are fine and don't create confusion, if written in a simplistic way. Long and rambling texts do create confusion, though. Images and videos may enrich reports, as I said. The point is how quickly others get the idea. An image will be quicker than a video. An image can show how something looks bad while a video can show how something behaves badly. A video can be like a long text, frustrating to go through while waiting to get to the point. -- You are receiving this mail because: You are the assignee for the bug.
