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@lemmy.worldM
      link
      fedilink
      arrow-up
      1
      ·
      2 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?

      • idunnololz@lemmy.worldM
        link
        fedilink
        arrow-up
        2
        ·
        edit-2
        2 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.