I’m getting green lines to the right and bottom of a lot of images. They also show up when saving the image, not just in the app.

They don’t show up when browsing on a web browser or when testing other Lemmy apps.

  • despoticruin@lemmy.zip
    2·
    5 days ago

    I also have this issue on Summit, though the lines don’t show up in saved photos. I assumed it was a bug in the image rendering libraries.

    • darklightxi@lemmy.worldM
      31·
      5 days ago

      Hey, just wanted to let you know that there should be a fix coming soon for this issue with v0.8.2! If the issue still persists afterwards, feel free to create a new GitHub issue.

      For some more context, the reason why the image isn’t loading properly is because it’s using .avif format (instead of the more typical .jpeg or .png) which Thunder did not account for.

    • MathematicalMagpie@lemmy.zipOP
      3·
      6 days ago

      I added the wrong image at first, and had to edit the post. That could be why.

      Maybe this will work?

      image

      Maybe not. Uploading images seems finnicky for me right now.

      EDIT: New issue. I can see the image in this comment in a web browser but not in the app.

    • Victor@lemmy.world
      1·
      6 days ago

      Voyager can.

      Zero for two for Thunder, eh.

      There were many small things like this which made me not use Thunder.

      • Cris@lemmy.world
        2·
        5 days ago

        They all have tradeoffs and will appeal to different people 🤷🏻‍♂️ personally the voyager ui is not for me, but I hope it serves you well as a client :)

        • Victor@lemmy.world
          1·
          5 days ago

          Yeah the Thunder UI looks better than Voyager’s. But when the UI doesn’t work. 🤷‍♂️

          Sync is the most beautiful UI out there, but sadly it’s abandoned.

  • darklightxi@lemmy.worldM
    1·
    5 days ago

    Hey there!

    Thanks for the report - I’m unable to reproduce this issue locally on my device so it would be great if you could possibly submit a new GitHub issue on this with additional details.