Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-65650

Importing a page to new editor makes the table scrollable after edit

      Issue Summary

      A page containing a table in the old editor is exported and imported to a new site which is using the fabric editor, the table is scrollable after the first edit of the page. This also happens for the tables present inside page property macros.

      Environment

      *Confluence Cloud
      *Fabric Editor

      Steps to Reproduce

      1. Create a table on the old editor with long text. (In the published mode, the table is not scrollable)
      2. Export this page and import it to another site which uses fabric editor.
      3. The table looks fine until the page is edited.
      4. On publishing the page after an edit, the table becomes scrollable.

      Expected Results

      Table rows content is displayed on the page without needing to scroll it

      Actual Results

      Table rows are scrollable.

      Workaround

      Need to edit the page and manually drag the rows for the desired width and then click on the * center* sign on the top right of the table.

            [CONFCLOUD-65650] Importing a page to new editor makes the table scrollable after edit

            Hi everyone,

            This is Anna from the Confluence team. Thank you for previously raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users.

            As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know by posting a comment and we will review.

            Thank you again for providing valuable feedback to our team!

            Best,

            Anna

            Anna Zakharevych added a comment - Hi everyone, This is Anna from the Confluence team. Thank you for previously raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Confluence users. As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know by posting a comment and we will review. Thank you again for providing valuable feedback to our team! Best, Anna

            Hi everyone,

            This is Anna from the Confluence team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the described behavior within our instances.

            We would like to get to the root cause of what you’re experiencing. Could you provide some more details or a screenshot to help us narrow down this case?

            We will keep this issue open for another 14 days, but if we don’t hear back by then we will need to close this out to focus on our upcoming roadmap for all Confluence users.

            Best,

            Anna

            Anna Zakharevych added a comment - Hi everyone, This is Anna from the Confluence team. Thank you for raising this bug and bringing it to our attention. After our investigation into this issue, we weren’t able to reproduce the described behavior within our instances. We would like to get to the root cause of what you’re experiencing. Could you provide some more details or a screenshot to help us narrow down this case? We will keep this issue open for another 14 days , but if we don’t hear back by then we will need to close this out to focus on our upcoming roadmap for all Confluence users. Best, Anna

            I would like to stress that the workaround is not acceptable with the amounts of content me and my customers (30+) have in our instances. The tables were designed with auto size in mind, we expect the content to remain readable after conversion.

            Maurice Pasman added a comment - I would like to stress that the workaround is not acceptable with the amounts of content me and my customers (30+) have in our instances. The tables were designed with auto size in mind, we expect the content to remain readable after conversion.

              Unassigned Unassigned
              kjaiswal Kritika Jaiswal (Inactive)
              Affected customers:
              12 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: