Content
View differences
Updated by Alexander Coles 3 days ago
### Context
`OpenProject::Common::BorderBoxListComponent` accepts a `header_padding:` option (`:inherit`, `:condensed`, `:default`, `:spacious`) that overrides the header's header's vertical padding independently of the box's box's own `padding:`. It says a second time what `padding:` already says, and each tier quietly carries a second effect: its own value for `--op-border-box-list-header-row-gap`, the gap below the header title line.
That coupling is what produced #AGILE-397. Moving the backlogs lists to `header_padding: :condensed` zeroed the gap in a header nobody was thinking about, and the loss only surfaced in the sprint headers of the Agile Backlogs page.
### Goal
Remove `header_padding:` so a list's list's padding is expressed once, through `padding:`.
### Notes
The only callers are the two backlogs components (inbox and work package card list). Beyond those, the change touches the component, its spec, the Lookbook previews and the Lookbook docs page.
Removing the option changes the rendered header `padding-block` for those callers, so this needs a visual pass over the backlogs pages rather than a spec-only check.
Suggested Agreed between Alexander and Henriette while fixing #AGILE-397: https://github.com/opf/openproject/pull/24865
`OpenProject::Common::BorderBoxListComponent` accepts a `header_padding:` option (`:inherit`, `:condensed`, `:default`, `:spacious`) that overrides the header's
That coupling is what produced #AGILE-397. Moving the backlogs lists to `header_padding: :condensed` zeroed the gap in a header nobody was thinking about, and the loss only surfaced in the sprint headers of the Agile Backlogs page.
### Goal
Remove `header_padding:` so a list's
### Notes
The only callers are the two backlogs components (inbox and work package card list). Beyond those, the change touches the component, its spec, the Lookbook previews and the Lookbook docs page.
Removing the option changes the rendered header `padding-block` for those callers, so this needs a visual pass over the backlogs pages rather than a spec-only check.
Suggested