Hi,

I'm using Confluence to maintain large pieces of technical documentation, where we document database tables field‑by‑field.

A concrete example is this page in our internal Confluence space:

• LOGINEXT table documentation
• ~280+ fields
• each row = 1 Oracle column (e.g. LXT_ABILITATOVALIDAZIONESDI, LXT_CHIUDE_BOLLONI, etc.)
• columns: Oracle field name, Oracle type, long functional description

In this kind of documentation we really need a table column type that strictly auto‑fits to its content width, without taking extra horizontal space.

Problem

Current Confluence table behavior:

• always tries to stretch columns to fill the full page width
• distributes the extra space between columns
• does not provide any per‑column option like “fit to content” / “no wrap”

For “code‑like” columns (field names, enum values, constants) this is a problem:

• the field name column becomes unnecessarily wide OR get wrapped on multiple lines, making it hard to read
• the useful columns (long descriptions) get less room
• the overall table becomes harder to read and to maintain
• it is impossible resize the columns in the designer in order to have a layout that renders nicely on any device or screen size: if you fixit for a certain display width, you break it for all the others.

What we would like is something closer to HTML tables with:

• width: auto
• white-space: nowrap
• no extra padding beyond the width of the longest single‑line cell in that column

Requested feature

Add a per‑column setting in Confluence Cloud tables, for example:

• “Fit to content (no extra width)”
  and/or
• “No wrap & fit to content”

Expected behavior:

• the column shrinks exactly to the width of its content (single line)
• Confluence does not force that column to grow just to fill the page
• ideal for columns with short, fixed identifiers (field names, codes, enums)

Typical use cases

• Database schema documentation (1 row per column)
• Permission/feature flag matrices (1 row per flag, short flag name + long explanation)
• Any table where:
  • first column = short identifier
  • other columns = long text, explanations, notes

In all these cases, having the first column “stick” to its content and not consume extra width would greatly improve readability.