This change reverts an older workaround because the underlying behavior has been addressed elsewhere. Gantt popovers should continue to open properly within the visible browser area, reducing awkward positioning near the edge of the screen.

This reverts commit ebeb633be737eb7bd614c2b474fafd65cd54f0ae.

This update fixes attachment display issues so uploaded file elements no longer overlap in affected screens, including signing flows. It also removes unnecessary styling, making the interface more reliable and easier to maintain without changing business workflows.

* = social_facebook,social_instagram,social_linkedin,social_twitter

This commits fixes:
* file DOM element don't overlap when git filename (`o_attachement` in `sign`)
* remove useless CSS

task-4333465

This update adjusts internal Helpdesk email-related tests after a related file name change. It helps keep automated checks reliable while preparing for upcoming email recipient improvements, with no expected change for day-to-day users.

List views can now apply a configured column width to action buttons. This gives business teams more control over list layouts, especially where button columns need consistent spacing or alignment.

Before this commit, it was not possible to set the width attribute in a list view arch on `<button>` nodes. This commit allows it.

One difficulty was that there's already some magic around button columns. Indeed, adjacent buttons in the arch are gathered in a single column. This doesn't map well with the width logic, as we want to be able to define a width on a button, which will thus define the width of its column. This can only work if the button is alone in its column. For that reason, when a button has a width, we do not group it with its potential adjacent buttons.

Task~4307553

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:




---
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

The rental website checkout test now targets the actually selected date instead of a visually highlighted date. This helps keep date selection behavior reliable as related date picker changes are introduced, reducing the risk of future checkout regressions.

This commit fixes a selector targetting the wrong property (datepicker "highlighted" date instead of the "selected" one).

This becomes relevant in an incoming commit in community changing the overall selection in date pickers.

Community: https://github.com/odoo/odoo/pull/184844
Part of task [3433683](https://www.odoo.com/odoo/project.task/3433683)

This fixes how adjustment values are handled in the Italian point of sale fiscal receipt flow. It helps ensure the fiscal printer receives the expected numeric value, reducing the risk of receipt printing errors for discounts or other item adjustments.

Change the adjustmentType prop type to Number instead of String

This update resolves an issue where nested lines within account reports were not fully unfolding, preventing users from seeing all related financial data. The fix ensures that all child lines are correctly expanded, providing a more complete and accurate view of financial reports. This improves data visibility and reporting accuracy.

This update ensures that images taken during quality checks linked to Manufacturing Orders (MOs) or Work Orders (WOs) are now correctly displayed within the quality check wizard. Previously, picture-type quality checks didn't show the associated image, which is now resolved to improve the visual clarity of quality control processes.

When opening a validated quality check from a MO/WO, if the type of the quality check is 'picture', the QC wizard should show the image taken.

This update corrects a discrepancy in how medical assistance work entries are handled within the payroll system. Previously, they didn't align with standard credit-time entries, leading to potential reporting inconsistencies. This fix ensures medical assistance entries now use the same DMFA code, improving accuracy and compliance.

The medical assistance work entry should be behaving like the credit-time and should have the same DMFA code.

Task: 4247631

Forward-Port-Of: odoo/enterprise#71872

This update ensures that only the necessary Electronic Data Interchange (EDI) fields related to Mexican tax regulations are displayed for Odoo companies with a Mexican fiscal country. This improves data accuracy and reduces clutter for users working with Mexican businesses, streamlining reporting and compliance.

We only need to shown MX EDI fields for move/invoices related to a company where fiscal country is Mexico, hide it for other companies.

Forward-Port-Of: odoo/enterprise#73623

A technical issue causing a traceback when managing addresses on the Odoo website for Colombian businesses has been resolved. The fix ensures consistent data access, preventing errors related to how address information is handled, improving the user experience for our Colombian customers.

Steps to Reproduce:
- Set up a website for a Colombian company.
- Go to the shop section.
- Purchase any product.

Issue:
- Traceback occurs when opening the address form for an existing or new address.

Cause:
- The error occurs because the form data for state_id, city_id, and other field is not consistently accessible, depending on whether values is a object or a dictionary.

Fix:
- Added checks to ensure fields like state_id and city_id are accessed only if they exist within values.

opw-4314031