Hi everyone,

Thank you for your patience. The Bitbucket Cloud team has successfully shipped this feature to our customers! Attached are some screenshots of what this will look like. We are going to go ahead and close out this BCLOUD ticket, but please feel free to continue adding questions, comments, or any other feedback here.

Best,
Luke

Gathering interest? really? only now?! When everyone moves away from Jira/Atlassian? Where were you years ago when we wanted this feature? What a shame! People have moved-on. This will be an excellent example on how to ignore your users for the offspring.

Got an email from this issues and decided I will log in to unwatch it finally, have moved on from Bitbucket ages ago and well this issue does explain a lot why...

How about coming up with a whitelist of HTML tags to allow, for example tags with "id" attribute, which are use to navigate within the page using A href's, I.e. in table of content scenarios?

This is really annoying. I wanted to add a code block in the README.md that uses UNIX manpage style syntax for describing what commands to run. Required me to use <pre> because I needed italics in the it. Works with other markdown viewers, but not in Bitbucket, where it's likely that other people will read it from.

Is there a feature to at least hide HTML tags that aren't supported like "a" tags ?

Very disappointing.

Disappointing.

Was just bitten by this today. Documentation is conflicting:

The markdowndemo repository states that you do not support HTML and use "safe mode", linking to a documentation page that has been down since January 2018. Relatedly, an archive of the linked page from a month after that section was last updated (February 2015) explicitly says that safe_mode is deprecated and should not be used. The current documentation for the python-markdown library that is the target of the broken link explains that safe_mode is deprecated and recommends bleach-allowlist as a replacement that still allows a subset of HTML.

The bottom of the Markdown Syntax Guide says you implement the Common Mark spec and says explicitly at the bottom that the file can contain "a restricted set of HTML tags" without specifying what. See this community post from 2018 for confusion around that guide.

This community post from 2017 states that we can use HTML tags and again links to the Common Markdown spec, which states the following:

Text between < and > that looks like an HTML tag is parsed as a raw HTML tag and will be rendered in HTML without escaping. Tag and attribute names are not limited to current HTML tags, so custom tags (and even, say, DocBook tags) may be used.

And further, earlier comments on this issue make mention of a Labs feature that supposedly supported HTML in Markdown as late as 2019, but I see no such Labs option in my account today.

For better or for worse, a core feature of Markdown is that it falls back to HTML, and many repositories have leveraged that to create richer READMEs. Bitbucket not supporting this is a notable deficit compared to competitors, and makes working with repositories originally hosted elsewhere rather unpleasant.

Please, give us at least an allowed subset of HTML to work with here.

This really needs to happen. My organization will not rework the 100s of pages of documentation because Bitbucket decided it's not going to do something that comes out of the box with git hub.

Is there an alternative for using <kbd> since it's not working right now?

I'd like to see <kbd> support in markdown. That tag in particular is often used for describing keyboard shortcuts and in the context of markdown is generally styled in css to look like a key.

Attachment 1586230559-Screenshot%202019-01-09%2009.42.32.png has been added with description: Originally embedded in Bitbucket issue #6930 in site/master

Attachment 2854748636-image.png has been added with description: Originally embedded in Bitbucket issue #6930 in site/master

Attachment 1624315727-Capture%20du%202019-08-08%2009-09-59.png has been added with description: Originally embedded in Bitbucket issue #6930 in site/master

Attachment 4260518973-Screenshot%202019-01-09%2009.41.59.png has been added with description: Originally embedded in Bitbucket issue #6930 in site/master

Attachment 2396139041-Capture%20du%202019-08-08%2009-10-27.png has been added with description: Originally embedded in Bitbucket issue #6930 in site/master

17ed8ab2acec It is available for me there :

• Go to Bitbuckets Labs

• Then you have some features.

However, I don’t know if Bitbucket Labs is available for everyone

bedwards@atlassian.com Nope, I don’t see it. Can you give me an explicit URL / screencap?

https://marketplace.atlassian.com/search?query=Embedded%20HTML%20in%20markdown

b3feacb2b7eb We do have quite a lot of feedback on this particular issue. I’m trying to recruit research participants for a large variety of studies we are starting to kick off and just saw this was a highly trafficked issue. I thought it would probably a good way to reach out to a larger group of users. I hope you can join our research panel!

Help us improve your experience by joining the Bitbucket Cloud Research Panel and participating in our research studies.

Jenifer, this feature is something most of your competitors have had for a very long time in one form or another. I can see how you could benefit from more datapoints in the global scheme of things. I wonder that maybe that’s simply how you are used to do things and have not yet considered alternative approaches. Still, from where I stand, I do not understand why in this particular instance you would need feedback beyond what has been already provided by us and evidence beyond what already exists on the market.

Hi all,

Thank you so much for your votes and comments on this issue. We’d love to learn more from you! Help us improve your experience by joining the Bitbucket Cloud Research Panel and participating in our research studies. Sign up here: https://forms.gle/XzrpgqrusuUVvAe37

— Bitbucket Cloud Design Team

The technology isn’t just there yet

I can agree with this sentiment. I fear that if I were to attempt adopting this feature, it may not actually be finalized ever. For me a “lab” is something that may or may not transpire at some future time, and can therefore not be relied upon. I understand it alleviates the pressure from the people working on it. Being safe from the unpleasant feeling of potential failure is always welcome. I know I welcome it.

At the same time, I want you guys at Atlassian to see that we are also in great pain around this feature, and have been for 6 years now. I am sure there is a mutually agreeable solution to this, such as full commitment to roll this feature out instead of a “lab”.

The technology isn’t just there yet

I logged in with my personal account (no special Atlassian permissions) and I see “Embedded HTML in markdown” as the third item in the list of Labs features. Is this not the case for you?

bedwards@atlassian.com I do not see any entries in Bitbucket Labs involving “Embedded HTML” at all – is this still the solution to this problem?

Please don’t bother preserving the idiosyncrasies Bitbucket’s current Markdown compiler.

Most Markdown editors/parsers/compilers use either something closer to John Gruber’s original Perl compiler, GFM, or CommonMark: specifically, VS Code, Atom’s markdown-preview package (which uses the marked compiler), iA Writer, and Byword. It is only after users upload documents that rendered in a manner consistent with one of those standards that we see those documents break in Bitbucket. The attempt to WYSIWYG away this problem with a live editor only makes the problem worse. Try, for example, to format text inside a link; it used to be easy, but now it’s impossible.

I also ask that we keep this ticket open until the beta markdown compiler is no longer just an experimental feature but baked into every aspect of Bitbucket, from READMEs to pull requests.

I've seen some opinions that BB cannot change markdown syntax to keep backward compatibility. Good point but that would leave us all stuck in 2013 forever. My humble suggestion is to have a first line of the markdown file that would indicate which markdown converter should be used. Something like:

markdown-parser: BitBucketNewAndImproved2019

Different or missing line would mean "classic" parser. Maybe there are better proposals but I have not seen them yet.

Does not work in the table cell.

@paulius-pupeikis - you can insert a line break or <br> in Markdown by putting two spaces at the end of a line.

This is not specific to Bitbucket, but is per John Gruber’s original Markdown spec.

<br> tag please?

I agree with Victor that this should not be closed. In my case I just want to be able to display a pipe "|" in a table. I still can't do this with the labs feature. Maybe we should all just make separate tickets for exactly the markup we want to use.

+1 for @VIJSluiter comment.

I think this issue should only be closed when the feature has made it to the default workflow.

Hey, don't discourage them. It's a step in the right direction nevertheless. After 6 long years, almost.

* changed status to closed

This is fixed with the Bitbucket Labs feature titled "Embedded HTML in markdown".

I doubt that. Not even considering the implementation problems with syntax highlighting and HTML entities, the feature is now enabled per-person. I cannot use HTML and be sure that my team sees what I'm seeing. I think this issue should only be closed when the feature has made it to the default workflow.

This is fixed with the Bitbucket Labs feature titled "Embedded HTML in markdown".

Issue BCLOUD-8755 was marked as a duplicate of this issue.

Another issue: I can't use syntax highlighting in the new version. Normally I use ```xml or ```c to start highlighting the code as XML or C (or JavaScript, or Matlab, or....) . That used to work, but seems to be broken in the new implementation. I'm switching back to the old markdown version.

Hi Brian,

This is not a functional fix for me. Within the <p></p> tags I cannot use markdown, and using something like *please* see<p>§9.1.3.4</p> for more details will (understandably) create a new paragraph with just the section name. The p tags are not a solution, it should work without that, as HTML entities are already standard since HTLML3.2, and can be used by other Markdown implementations without problems (I'm using VSCode with Markdown Preview Enhanced as editor for markdown, Mkdocs for documentation, Pandoc with reveal.js for presentations). Please confer to the standard so that I can re-use documentation without worrying about the platform.

<small>I'd even suggest to go a step further and add the LateX rendering between $ signs.... </small>

Hi Victor, Thanks for trying it out. Getting HTML entities to render is finicky, but possible. You must wrap the HTML entities in p tags. I have an example at https://bitbucket.org/bmedwar/markdown-examples/src/master/README.md .

Where this input...

(a newline at the end of the file is important) renders as...

I tried this. First: thanks for implementing it, at least it's an acknowledgement to all the people asking for this feature.
Second: please also support HTML entities , I'm using a lot of μseconds , which should read as microseconds, or MΩ which should read as megaohm.... I can now finally use superscript and subscript using HTML, but the subset of this feature is too limited at this moment....

If you look on the "Bitbucket Labs" page, you will see a new Beta feature named "Embedded HTML in markdown". Be aware that it switches to a completely new markdown rendering backend. You will get support for some embedded HTML tags, but you might need to rework your markdown files to handle differences with the two rendering packages. Most notably the new one is more strict in requiring a blank line after headers.

I think @hyamacube nailed it with this one:

They know how to implement it, but there is some religious reason why they won't

At this point it is beyond ridiculous that this has not yet been implemented. Especially considering that this feature is simply hidden behind a configuration variable. I know that Atlassian has invested a lot of time in improving the UI recently but honestly... who cares about the UI improvements if they are at the expense of the user experience?! I have had to disable almost all of the new UI displays because they are either half baked and still seem very much in beta, or they removed a key piece of functionality.

Here's another related issue also opened back in 2013 to support task lists in markdown: BCLOUD-8586

These are not requests for massive, innovative features. They are minor requests to bring Bitbucket into feature parity with competitors with features that they have been missing for years. Stop screwing the user, Atlassian.

Any update on this?

Neither org-files, nor markdown or html exports are working in bitbucket.

As long as at least this feature is not implemented, this product has a big no-go sticker at it from my company's perspective. Even small systems like gitea support this, it's a joke that no one attends to this feature for 5+ years.

+1 Github is so much ahead with this kind of things

The new WYSIWYG editor for comments makes things worse. There are some new un-allowed things like backticks for preformatted code inside links.

Ok, so I no longer use BB, so you can safely ignore my comment if it annoys you. And I guess I'm going to be a bit obnoxious.

The last feedback from the staff was that:

We are currently gathering feedback

If you scroll up from that point and look at older messages, you will see that many issues have already been marked as duplicates of this issue. There's been a fair deal of feedback here, and a fair deal of feedback in the duplicates. We are entering the sixth year since this issue was first identified. The person managing this project should step down.

I cloned a repo into my local one. This repo has a readme file: https://github.com/wprig/wprig/blob/master/README.md. Unfortunately bitbucket, will not renders it. It looks more than broken.

Would be nice to support the <summary> tag so we can have collapsible regions in markup as well, like in Github.

I want Bitbucket to parse this:

^{<mark>Opsional</mark>}