You can see this minor bug in the picture that I shared here.

I don’t know if dev is aware, but as I didn’t see anyone commenting about it I wanted to share it :)

  • idunnololz
    shield
    M
    link
    13 months ago

    I have a fix for this in the latest version. Please confirm that the issue is fixed. Thank you!

    • kratoz29OP
      link
      fedilink
      English
      23 months ago

      Hi, unfortunately the bug of this thread is not fixed for me in version 1.39.0, I do see the link background has a better visibility with white theme though.

      • idunnololzM
        link
        23 months ago

        I figured it out. It seems this bug is somehow instance specific. I was able to finally reproduce it by using an account on lemm.ee. I’ll work on a fix for the next update.

        • kratoz29OP
          link
          fedilink
          English
          13 months ago

          Excellent! It never crossed my mind to try it out in another instance, well waiting for the next version then, sorry for causing you troubles with this minor bug 😅

          • idunnololzM
            link
            23 months ago

            I’m just glad I finally got a reproduction.

  • idunnololzM
    link
    33 months ago

    I can’t reproduce this issue locally. Could you please DM me with your settings? To generate a shareable settings code, navigate to Settings > Import & export settings > Export settings > Copy to clipboard. Thank you!

    • kratoz29OP
      link
      fedilink
      English
      2
      edit-2
      3 months ago

      Hi, I just sent you the info, quite a handy feature BTW :)

      • idunnololzM
        link
        13 months ago

        This is very odd. Even with your settings I am still unable to reproduce the issue. Do you know which version of Android you are running on your phone?

        • idunnololzM
          link
          2
          edit-2
          3 months ago

          Tracing the code I can see one possible way for this to happen however I was never able to get that code path to trigger in my testing. Does this bug occur naturally or did you have to perform some action(s) for you to get this bug? I’m curious about the reproduction steps.

          In any case, I handled the one case that I found where this can technically happen. Hopefully it will fix the issue.