If you come across something that doesn’t work pop it here

  • can@sh.itjust.worksEnglish
    4·
    4 months ago

    Any progress being made here? I was really hoping that not being able to view certain communities such as !newbrunswick@lemmy.ca would be considering bad enough of a bug to bring a little development back.

  • tb_@lemmy.worldEnglish
    3·
    6 months ago

    Code blocks in quotes appear a little funky.

    Some line of code

    
> Extended quote
> ```
More code

    Further extended quote

  • can@sh.itjust.worksEnglish
    3·
    4 months ago

    I’m not sure if you’re still monitoring this or if I should make new thread.

    I just encountered a comment where they included a link with brackets in the url and it didn’t parse for me in Sync. I assumed it needed escape characters , which did make it a working link for me in app, but I got curious and checked the website and the original link worked fine there. Maybe the Lemmy web ui will escape characters in links by default?

  • cyberic@discuss.tchncs.deEnglish
    1·
    6 months ago

    Footnotes are weird? Maybe this post is weird?

    https://lemmy.world/comment/8880898

    Sync view:

    Mobile web view:

    Device information

    Sync version: v24.03.26-14:56    
Sync flavor: googlePlay    

Ultra user: true    
View type: Slides    
Push enabled: false    

Device: d2q    
Model: samsung SM-N975U    
Android: 12
  • Aido@lemmy.worldEnglish
    1·
    3 months ago

    Funny stuff is happening with the spoilers in this comment, they aren’t rendering as spoilers on the first two but tapping the actual spoilers removes the broken spoiler characters around the first two lines? Really strange: https://lemmy.world/comment/10822445

  • Risk@feddit.ukEnglish
    1·
    2 months ago

    Posts are not being marked as read, unless the comments are opened.

  • Stovetop@lemmy.worldEnglish
    1·
    6 months ago

    !spoiler spoiler Test Comment

    with line breaks!<

    
with line breaks!<```

Saw this comment in the wild which does not appear correct in Sync.

https://discuss.tchncs.de/comment/8334366

In Sync it looks like this:

![](https://lemmy.world/pictrs/image/a660f68f-f78b-41a8-ae15-17a8cd896c3e.jpeg)

On Lemmy via browser, it looks like this:

![](https://lemmy.world/pictrs/image/ed917b91-cdf6-401a-92e0-01462790b8ce.jpeg)
  • Voxtopass@lemmy.worldEnglish
    1·
    6 months ago

    Furigana (a feature of Japanese text) is supported by Lemmy on the web but doesn’t work in Sync. It’s not a part of core markdown but Lemmy uses a plugin.

    Here’s an example post showing how to use it. https://programming.dev/post/530608

    Here’s what it should look like:

    And here’s Sync:

  • Coelacanth@feddit.nuEnglish
    1·
    6 months ago

    Spoiler formatting was a big one, Lemmy wants to do it like this, I think:

    Some paragraph text.

    Spoiler Title

    Some spoiler elements

    Other paragraph text.

    EDIT: the main issue being Sync not displaying the spoiler title properly

      • Zagorath@aussie.zoneEnglish
        1·
        6 months ago

        sharing it to someone without sync

        The bang syntax will work much better for anyone on Lemmy itself, regardless of which instance they’re on or which client they use, while the URL syntax is better when users want to share a link to a community off-platform.

    • Zagorath@aussie.zoneEnglish
      2·
      6 months ago

      I installed Sync just to test this. To me, that’s displaying with “not” superscript but not “working”. On web, it just doesn’t work at all (this is due to the markdown library lemmy-ui uses not allowing spaces).

      Suspect ~subscript will~ also not work. Curious about struck-out text.

      • Zagorath@aussie.zoneEnglish
        1·
        6 months ago

        Okay subscript didn’t work on lemmy-ui or Sync. Struck out is fine.

        How about single-word subscript? edit: yup, works in lemmy-ui, not in Sync.