Skip to content

[20.0][MIG] report_qweb_element_page_visibility: Migration to 20.0 - #1223

Open
arantxa-s73 wants to merge 35 commits into
OCA:20.0from
Studio73:20.0-mig-report_qweb_element_page_visibility
Open

arantxa-s73 wants to merge 35 commits into
OCA:20.0from
Studio73:20.0-mig-report_qweb_element_page_visibility

Conversation

@arantxa-s73

Copy link
Copy Markdown
Contributor

Migration of report_qweb_element_page_visibility from 19.0 to 20.0

Sebastien LANGE and others added 30 commits October 27, 2026 16:23
…age_visibility module

These classes cause the element to be visible when the document is only a single page long (for single-page) or when it's multiple pages long (for multi-page). This is especially useful for page counters, which can be hidden when there's only a single page.
…sibility

the visibility attribute with the hidden option hides the element but
don't free the space.

A common use case is to have a specific header for the first page and
another for the other pages. With visibility: hidden the second header
cannot take the first one place and will keep a huge margin.
One solution is to use the display:none instead.
@OCA-git-bot OCA-git-bot added series:20.0 mod:report_qweb_element_page_visibility Module report_qweb_element_page_visibility labels Oct 27, 2026
@arantxa-s73 arantxa-s73 mentioned this pull request Oct 27, 2026
22 tasks
@arantxa-s73
arantxa-s73 force-pushed the 20.0-mig-report_qweb_element_page_visibility branch from 265b719 to 205502e Compare October 27, 2026 16:42

@Reyes4711-S73 Reyes4711-S73 left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.