4

Right now, debug info (Browser/OS/Active Kagi region setting/What Kagi server you connect) must be manually entered. This increases the chance this info is not added or added incorrectly. For example, I did not realize the Kagi region was not included (or even requested) when I copy-pasted the bit from the control center.

Therefore, I suggest:

  1. Putting all debug info together in the same place on the control center so they can be copy-pasted together.
  2. Adding Browser/OS. Either the user agent string, or a more friendly version of it. Note this will probably give much more detailed (sub) version information compared to manually entering it.
  3. Adding a button that copies this info to your clipboard
  4. Ideally: The "send feedback" link opens https://kagifeedback.org/ with the bug report composition form pre-filled with this information. This would eliminate the need to switch from https://kagifeedback.org/ to find the debug info, then back to https://kagifeedback.org/ to fill it in.
  • Vlad replied to this.

    leftium We do not know if you want to report a bug or make a suggestion when clicking the link so such assumption (that it is a bug which needs debug info) can not be made (it is 50/50).

    Browser/OS from UA is notoriously misleading and some browser provide wrong version on purpose.

    Finally not sure where to put the button as control center is a bit too crowded already.

    Simplifying bug reporting makes sense from a high level perspective, looking for execution steps that are doable.

      We do not know if you want to report a bug or make a suggestion when clicking the link

      Good point. I can think of several ways to allow the user to choose between a bug and suggestion:

      1. Turn the "Send Feedback" link into a menu/combo button.
      2. When the user clicks "Send Feedback," send them to a dedicated "bridge/landing" page (instead of the front page) that only has the two buttons (bug/suggestion) and user-friendly instructions. (The first time I clicked "Send Feedback" I was a little confused because I wanted to report a bug, but I was presented with a list of bugs.) This would be a great place to put the debug info with UI for copying to the clipboard. Also could be implemented as an overlay/modal dialog over the Kagi page itself.
      3. Allow the user to switch between bug/suggestion on the form itself.
      4. Merge the suggestion template with the bug template (auto-tagging is not possible, though)

      Browser/OS from UA is notoriously misleading and some browser provide wrong version on purpose.

      Perhaps the UA is still better than no data at all?


      Finally not sure where to put the button as control center is a bit too crowded already.

      It doesn't have to be a button, and I don't think it takes up that much space. Some examples:

      text link:

      button-label with icon: (https://cc.leftium.com/)

      just icon

      (couldn't remember any examples...)


      Finally, my Kagi control panel seems to have plenty of space:

      Mobile requires scrolling, but I think a "Copy debug info" link would fit next to "Status"

      No one is typing