A suggestion for Bug Reporting



  • As I see you Team usually use a precompilated form to prompt user for a bug, this one:

    Please report the bug.
    If you found a bug, please report the issue to the developers to fix it.
    How to do a bugreport for Vivaldi
    Report each bug seperately at https://vivaldi.com/bugreport/
    Describe the issue as precise as you can.
    Add some information about extensions you use.
    Add information about the operating system and version you use.
    if you have problems with video or audio give us information about your installed codecs and graphics card/GPU.
    Add a link to a testpage where the issue comes up and can be tested.
    After reporting the issue, you will receive a confirmation mail from the bugtracker.
    In a reply to this mail you can add more information and files (like screenshots or testcases) as attachments and it will be added automatically to bug report.
    If you have questions about the bug please ask in forum first and do not forget to post the VB-XXXXX bug number (you can find it in confirmation mail).

    So, why don't put this questions directly to the bug link?
    I ask this because, actually, the questions asked on the link are less, and do not coincide in all with the previous questions:

    Summary *
    The issue explained in one sentence
    Address (URL) where it occurred, if relevant"
    example: http://vivaldi.com
    Describe in steps how to reproduce the bug
    Steps to reproduce the bug
    What did you expect to happen *
    The expected result of the steps
    What had actually happened *
    The actual result of the steps
    Vivaldi version *
    1.91.867.48
    The latest stable release of Vivaldi is 1.10 - Download it here if you are using an older version.
    Operating system *
    Email (in case we need to get in touch) *
    Your email adress



  • @Marko-Indaco
    Good idea.

    The hint to deactivate all extensions and reload the "offending" page (if any) after that would help to narrow down the problem too.

    • If the bug is still there, it is not extensions related.
    • If not, it is extension related and it would be helpful if the "Extensions" table, which can be found under
      vivaldi://net-internals/#modules
      would be copy/pasted into the bug report.

    Operating system and browser version are only important if the user reports with a different OS or browser than the Vivaldi install that shows the bug, otherwise the UA string already contains the necessary information.

    Additionally the hint that the form supports some parts of the Markdown similar to this forum would help too, e.g. "# " in front of lines gives ordered/numbered lists and "- " in front gives unordered lists, without the quotes, of course :)

    Example with a dash and a space in front of the text:

    • go to the example page
    • click on the button (description where, especially if it is in a different language than English)
    • do this
    • do that

    That is much more legible and the chances that the bug gets fixed fast will be much higher than if the user writes a 1000 words novel (yepp, that happened too. It was really hard to find the 2 sentences that actually described the bug)

    ... and the most important thing:
    Try to find the minimal steps that are necessary to make the bug reliably reproducible, if possible.(Yes, there are so called "sometimes bugs" too, i.e. bugs that don't happen always. Very hard to reproduce.)

    And another thing:
    If you are no English speaker and use an automated translator like the ones from Google or Microsoft:

    Please add the original text in your native language below the auto translated version.

    Sometimes the automated translators mangle the texts that much, that it is almost impossible to understand what the user wanted to tell us. There are testers that speak several languages who in doubt might be able to read the original.

    The English version is of course still mandatory, despite rumors that the developers only speak important languages like e.g. Assembler, C++, Javascript, Python, etc. pp.
    (OK, that was geeky. I hope none of the Devs reads this :D )



  • @Marko-Indaco said in A suggestion for Bug Reporting:

    As I see you Team usually use a precompilated form to prompt user for a bug, this one:
    Please report the bug.
    If you found a bug, please report the issue to the developers to fix it.
    How to do a bugreport for Vivaldi
    Report each bug seperately at https://vivaldi.com/bugreport/
    Describe the issue as precise as you can.
    Add some information about extensions you use.
    Add information about the operating system and version you use.
    if you have problems with video or audio give us information about your installed codecs and graphics card/GPU.
    Add a link to a testpage where the issue comes up and can be tested.
    After reporting the issue, you will receive a confirmation mail from the bugtracker.
    In a reply to this mail you can add more information and files (like screenshots or testcases) as attachments and it will be added automatically to bug report.
    If you have questions about the bug please ask in forum first and do not forget to post the VB-XXXXX bug number (you can find it in confirmation mail).

    I believe that is @Gwen-Dragon 's own version whereas the linked page is the "official" Vivaldi form.
    I think hers is better



  • Argghhhh! Ouuuh! Ahhhh! That is not a official howto.
    Hmmpfff, where is the next cave to hide for my bad explanation how to report bugs.
    My own bad translation from my german fast working (overcloked!?) brain 0.98. I am sorry. :blush:
    That was done quickly, some months ago and i thought is was ok. Nobody told me that it was bad.

    I am a ol' programming gal and dragoness with some loss of english practice. Please have mercy.

    But please give me a better one so i can put it in my Vivaldi notes to add the next time a user would need such How-tos.



  • If you have a better (i. e. understandable and in correct english) text to be added to the official bug tracker, please report that as a bug and add the text in an attached text file to a mail reply to the reported "bug".



  • @Gwen-Dragon :D to me are pretty clear you're questions for bug reporting, and are better than the "official" ones ;)



  • @Gwen-Dragon No no no, you mis-understood.
    @Marko-Indaco nad @QuHno were saying that your version was better than the actual bug report page :smiley_cat:

    I was just making sure you received the deserved credit for it.



  • @Marko-Indaco @TbGbe @QuHno Oh, many thanks for the positive feedback.

    Good to know that a howto created in a rough and fast way by a non-native english speaker like me is good enough for others.
    Feeling proud!


Log in to reply
 

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.