Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-40050

Sticky table header for table inside a page layout/section.

    • Icon: Suggestion Suggestion
    • Resolution: Won't Do
    • None
    • None
    • We collect Confluence feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for Confluence Server. Using Confluence Cloud? See the corresponding suggestion.

      Currently, Table headers aren't sticky when the table is created inside a page layout.
      Therefore, it would be better to have the table header to stick on the top of the page even if the table is created in the page layout that is divided into sections.

            [CONFSERVER-40050] Sticky table header for table inside a page layout/section.

            DSell added a comment -

            I feel this is a big gap. How can freezing the header row not be standard and work all the time without tricks or addons?

            @Atlassian... I am a big proponent of your tools, but it is this type of stuff that upsets many users. It is this stuff that is heard at the EC level, not always the good about your tools.

             

            Best,

            David

            DSell added a comment - I feel this is a big gap. How can freezing the header row not be standard and work all the time without tricks or addons? @Atlassian... I am a big proponent of your tools, but it is this type of stuff that upsets many users. It is this stuff that is heard at the EC level, not always the good about your tools.   Best, David

            This is a severe limitation, even though it is known!!!

            We use tables a lot, and since the introduction of page layouts, I've replaced in our global page models all Section and Column macros with page layouts. Page layouts are a lot more intuitive, so my feeling was that page layouts would outlast Section and Column macros.

            As a workaround, we're already using the Table Enhancer macro. However, it has its disadvantages in Edit mode, such as the cursor jumping to the top of the page when you try to select text, etc. For that reason, I would have expected to replace it with the built-in native table functions - that is, should they work within a page layout.

            So, if I want sticky headers, the choice I have is: either I use Section/Column macros, or I use the tableenhancer macro within a page layout.

            Those choices are clear to me as a Confluence admin, but it just contributes to make things a little more confusing – and less visually intuitive – for our end-users. Which is rarely what you aim when using a tool that proudly states its ease of use.

            I can't believe this has been tagged as a "Won't do"...

            Normand Brousseau added a comment - This is a severe limitation, even though it is known!!! We use tables a lot , and since the introduction of page layouts, I've replaced in our global page models all Section and Column macros with page layouts. Page layouts are a lot more intuitive, so my feeling was that page layouts would outlast Section and Column macros. As a workaround, we're already using the Table Enhancer macro. However, it has its disadvantages in Edit mode, such as the cursor jumping to the top of the page when you try to select text, etc. For that reason, I would have expected to replace it with the built-in native table functions - that is, should they work within a page layout. So, if I want sticky headers, the choice I have is: either I use Section/Column macros, or I use the tableenhancer macro within a page layout. Those choices are clear to me as a Confluence admin, but it just contributes to make things a little more confusing – and less visually intuitive – for our end-users. Which is rarely what you aim when using a tool that proudly states its ease of use. I can't believe this has been tagged as a "Won't do"...

            Atlassian update

            Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. Thanks again.
            Regards,
            Confluence Product Management

            Adam Barnes (Inactive) added a comment - Atlassian update Thank you for raising this suggestion. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now. Sometimes potentially valuable tickets do get closed where the Summary or Description has not caught the attention of the community. If you feel that this suggestion is valuable, consider describing in more detail or outlining how this request will help you achieve your goals. We may then be able to provide better guidance. Thanks again. Regards, Confluence Product Management

              Unassigned Unassigned
              dazmi Dayana
              Votes:
              1 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated:
                Resolved: