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

  • tb_@lemmy.world
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    8 months ago

    Code blocks in quotes appear a little funky.

    Some line of code

    
    > Extended quote
    > ```
    More code
    

    Further extended quote

  • can@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    2
    ·
    6 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.

  • Risk@feddit.uk
    link
    fedilink
    English
    arrow-up
    1
    ·
    4 months ago

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

  • Gorgritch_Umie_Killa@aussie.zone
    link
    fedilink
    English
    arrow-up
    1
    ·
    19 days ago

    Hi!

    Moderator from !perth@aussie.zone here.

    Just been playing around using the spoiler tags as makeshift drop down lists in the sidebar for the Perth/WesternAustralia community, and noticed the ‘spoiler’ markdown formatting isn’t recognised in the ‘about’ page on the Sync app. :)

  • Aido@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 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

  • can@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 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?

  • Stovetop@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    8 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)
    • SanguinePar@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      8 months ago

      I think a way to make them work is to add two spaces after each line. Here’s a test…

      • Line one
      • Line two
      • Line three

      Hopefully that works.

      It did :-)

      • CrayonRosary@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        8 months ago

        That’s a placebo and it’s not doing anything. Bulleted lists never need two spaces at the end of each line. You only use two spaces at the end of line that are not in bulleted or numbered lists.

        The bug is that Sync requires a blank line before you start the bulleted list. The Lemmy website doesn’t require that.

        Here is your comment with no spaces at the end of each line:

        spaces after each line. Here’s a test…

        • Line one
        • Line two
        • Line three

        See? It still works fine.

        Now here’s an example of what two spaces do.

        The first sentence below has a new line after each word but no spaces. The second sentence has two spaces and a new line after each word. The spaces force a line break to be rendered.

        This Is Not A List

        This
        Is
        Not
        A
        List

        Source of the above:

        This 
        Is 
        Not 
        A 
        List
        
        This  
        Is  
        Not  
        A  
        List
        

        This feature of markdown was implemented to prevent text from emails and such from wrapping in funny ways when pasted into a comment (or whatever). Old emails often force line breaks after 80 columns of text and it looks goofy when viewed in a modern web browser if those line breaks are kept, so they are ignored. To preserve the line breaks, you add two spaces at the end of each line. That or you might prefer to write paragraphs with a hard wrap at some column, but other people shouldn’t have to suffer that.

        Adding the two spaces to lines in a bulleted list does nothing useful, but it also doesn’t break it, so of course it works.