Using backticks in Markdown readmes breaks overview

Gabriel Gilder avatarGabriel Gilder created an issue

When I include backticks in a Markdown-formatted readme (to indicate code or preformatted content), everything on the rest of the line starting from the backtick is not displayed on Bitbucket's overview page for the repo.

Comments (14)

  1. Nathan Durnan

    I am having a similar issue with the overview readme for my TimestampMod repo (https://bitbucket.org/nedmech/timestampmod). It was displaying nicely up until sometime between yesterday and today.

    Looking at the syntax highlighting in the README.md source (https://bitbucket.org/nedmech/timestampmod/src/24fc57ff28ca/README.md), it looks like it might have something to do with escape characters. On line 28, I have a file path in double-quotes:

     ...  (usually "C:\Program Files\TortoiseHg\"). ...
    

    The syntax highlighting up to that point looks OK, but it fails to return to normal text between the final ") characters. It is acting like the \" is being treated as an escape sequence and not registering the close of the first double-quote. Beyond that line, the display formatting on my overview page is completely messed up.

    It displays just fine when I drop the README.md contents into any other Markdown converter or display tool (such as http://daringfireball.net/projects/markdown/dingus), so I'm thinking there's something that has changed here at BitBucket that has messed up the Markdown parsing. I tried added explicit escape characters to my markdown, but that didn't seem to help either (https://bitbucket.org/nedmech/timestampmod/src/d8c3e4dc134e/README.md).

    BitBucket seems to be incorrectly parsing links as well. All of my links in my README are no longer being displayed, and nothing after a link on a line is displayed either. Something is very broken.

  2. Brodie Rao

    This should be fixed now. We pushed out a change to fix an XSS issue in our Markdown rendering, but in the process ran into a bug in the library we use. We're now running a newer version.

  3. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.