Skip to content

[19.0][MIG] web_widget_section_and_note_text_scrollable: Migration to 19.0#3373

Open
yankinmax wants to merge 3 commits intoOCA:19.0from
camptocamp:19.0-mig-web_widget_section_and_note_text_scrollable
Open

[19.0][MIG] web_widget_section_and_note_text_scrollable: Migration to 19.0#3373
yankinmax wants to merge 3 commits intoOCA:19.0from
camptocamp:19.0-mig-web_widget_section_and_note_text_scrollable

Conversation

@yankinmax
Copy link
Copy Markdown
Contributor

No description provided.

@yankinmax yankinmax force-pushed the 19.0-mig-web_widget_section_and_note_text_scrollable branch 7 times, most recently from 48e5a8d to 11eeb7c Compare November 26, 2025 07:51
Copy link
Copy Markdown

@jcoux jcoux left a comment

Choose a reason for hiding this comment

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

Code LGTM 👍

Don't forget to squash fixup

@yankinmax yankinmax force-pushed the 19.0-mig-web_widget_section_and_note_text_scrollable branch from 11eeb7c to d0f5a48 Compare November 26, 2025 09:30
@yankinmax
Copy link
Copy Markdown
Contributor Author

Hello @ivantodorovich
I need your help here. I've always a small "cell" size. Scrollable but small.

@yankinmax yankinmax force-pushed the 19.0-mig-web_widget_section_and_note_text_scrollable branch from d0f5a48 to 850b6b9 Compare November 26, 2025 09:42
Comment on lines +7 to +11
.o_field_product_label_section_and_note_field,
.o_field_product_label_section_and_note_cell,
.o_field_product_label_section_and_note_cell textarea {
height: auto !important;
}
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

I'm a (s)css noob, but I think height is anyway redefined in o_field_product_label_section_and_note_cell and o_field_product_label_section_and_note_cell textarea below.

Suggested change
.o_field_product_label_section_and_note_field,
.o_field_product_label_section_and_note_cell,
.o_field_product_label_section_and_note_cell textarea {
height: auto !important;
}
.o_field_product_label_section_and_note_field {
height: auto !important;
}

@imlopes
Copy link
Copy Markdown

imlopes commented Feb 23, 2026

Hello @yankinmax
Could you check please the comment from Vincent?

Thanks.

@yankinmax
Copy link
Copy Markdown
Contributor Author

Hello @imlopes
I would like to rebase and update this PR, but don't have time now.
If you're able to update this PR I would highly appreciate.

Copy link
Copy Markdown
Contributor

@alexey-pelykh alexey-pelykh left a comment

Choose a reason for hiding this comment

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

Thanks for the migration, Maksym.

CSS class targeting looks correct for 19.0 -- the widget moved to account and uses o_field_product_label_section_and_note_field / o_field_product_label_section_and_note_cell now. The SCSS-only approach (no JS/OWL needed) is clean.

One minor note: the .pot file still says Project-Id-Version: Odoo Server 17.0 -- not blocking since the OCA bot regenerates it, but worth noting.

I'd echo vvrossem's observation on the first rule: the height: auto !important for .o_field_product_label_section_and_note_cell and its textarea is immediately overridden by the rules below, so narrowing that selector would trim some dead CSS. Not blocking either way.

LGTM overall.

@OCA-git-bot
Copy link
Copy Markdown
Contributor

This PR has the approved label and has been created more than 5 days ago. It should therefore be ready to merge by a maintainer (or a PSC member if the concerned addon has no declared maintainer). 🤖

@yankinmax yankinmax force-pushed the 19.0-mig-web_widget_section_and_note_text_scrollable branch from 850b6b9 to 39be420 Compare March 3, 2026 13:39
@yankinmax
Copy link
Copy Markdown
Contributor Author

Hello @OCA/web-maintainers can you pls merge this PR?

@yankinmax
Copy link
Copy Markdown
Contributor Author

Hello @etobella @hbrunn can you pls take a look at this PR and possibly merge?

Copy link
Copy Markdown
Contributor

@ivantodorovich ivantodorovich left a comment

Choose a reason for hiding this comment

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

Hey @yankinmax

It seems to work in edit mode, but not on read mode.

Moreover, in edit mode, it's moving the field as a column instead of keeping it below.. making the UI a bit weird. (possibly due to the display: flex)

Screen.Recording.2026-03-16.at.10.26.16.AM.mov

@yankinmax
Copy link
Copy Markdown
Contributor Author

Hey @ivantodorovich
It was ok 😞
Thanks for checking! I'll take time to update!

@ivantodorovich
Copy link
Copy Markdown
Contributor

I checked on runboat (Odoo CE)

Beware if you check on Odoo EE, sometimes different styles are applied.
However, the module must work on both versions.

@yankinmax yankinmax force-pushed the 19.0-mig-web_widget_section_and_note_text_scrollable branch 2 times, most recently from e2a3c5d to a1c8560 Compare March 26, 2026 12:54
@yankinmax yankinmax force-pushed the 19.0-mig-web_widget_section_and_note_text_scrollable branch from a1c8560 to 8533025 Compare March 26, 2026 13:00
@yankinmax
Copy link
Copy Markdown
Contributor Author

Hello @ivantodorovich
This PR is fixed, thanks for the suggestion and check

Copy link
Copy Markdown

@vvrossem vvrossem left a comment

Choose a reason for hiding this comment

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

code LGTM

@yankinmax
Copy link
Copy Markdown
Contributor Author

Hello @ivantodorovich
Can you pls check this migration again and possibly trigger merge?

Copy link
Copy Markdown
Contributor

@ivantodorovich ivantodorovich left a comment

Choose a reason for hiding this comment

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

Thanks @yankinmax . Getting there

.o_field_product_label_section_and_note_cell textarea {
display: block;
width: 100%;
height: 10em !important;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Why forcing the height? I understand the max-height, cause that's the whole point of this module (have it scroll instead). But not this.

This is probably causing the following unwanted behavior.
Compare against standard Odoo here:

This PR runboat:
https://github.com/user-attachments/assets/2d6c1ca3-0969-4991-b168-9b329056d9e1

Odoo's runbot:
https://github.com/user-attachments/assets/c8bed633-957b-4d8e-8fde-4b016895512c

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@yankinmax , not sure to really understand why you pinged me here. Do you need a functional advice? Or is it to point me the issue we are facing?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Hello @alicedsp
I thought I've fixed the PR and I wanted you to make a functional review here.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

@yankinmax , LGTM on the following runbot: [http://oca-web-19-0-pr3373-8533025579a0.runboat.odoo-community.org/odoo/discuss ]
A description can be added on the SO, if it is long the user will need to scroll to be able to see it completely in both display and edit mode.

2. Don't change its height.
*/
.o_field_product_label_section_and_note_cell:not(:has(textarea)) {
display: block !important;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

This seems redundant AFAICS

*/
.o_field_product_label_section_and_note_cell:not(:has(textarea)) {
display: block !important;
max-height: 10em;
Copy link
Copy Markdown
Contributor

@ivantodorovich ivantodorovich Mar 30, 2026

Choose a reason for hiding this comment

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

Maybe height: auto !important is needed here, too.

Cause I'm noticing some programmatical height style property being set, not sure from where, that's sometimes conflicting with the scroll -- assuming you remove the fixed height: 10em in the textarea, like suggested here: #3373 (comment)

Screen.Recording.2026-03-30.at.12.17.22.PM.mov

Not sure if height: auto is the best solution, but otherwise we need to investigate who's setting this fixed height and how it's computing it and why it's falling short -- cause if it were a few pixels taller we wouldn't have this issue.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants