Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-20545

Incorrect alignment on Markdown tables on PR description

XMLWordPrintable

      Issue Summary

      Markdown tables very much differ from their preview view when compared to the actual results in the PR body.

      As an example, the following table should have each of its columns with different alignments:

      right aligned | left aligned and long | center aligned
      --:|--------------|:--:
      1.|Lorem ipsum dolor sit amet, consectetur adipiscing elit.|stuffs
      2.|Lorem ipsum dolor sit amet, consectetur adipiscing elit.|stuffs
      3.|Lorem ipsum dolor sit amet, consectetur adipiscing elit.|stuffs
      

      When checking the preview view, the following can be seen, which is the expected behavior for this table:

      When actually creating the PR and checking the table, however, the formatting will always be left-aligned:

      Steps to Reproduce

      1. Create a new PR;
      2. In the description, add the following Markdown table for example:
        right aligned | left aligned and long | center aligned
        --:|--------------|:--:
        1.|Lorem ipsum dolor sit amet, consectetur adipiscing elit.|stuffs
        2.|Lorem ipsum dolor sit amet, consectetur adipiscing elit.|stuffs
        3.|Lorem ipsum dolor sit amet, consectetur adipiscing elit.|stuffs
        

      Expected Results

      The expectation, in this case, is for the rendered table to align the columns just like the preview view does, like this:

      Actual Results

      The rendered table will always be rendered with left-aligned columns:

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

              Unassigned Unassigned
              lmontiel@atlassian.com Leonardo M
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: