Browser-based test failures now save screenshots automatically in a temporary location, making it easier to diagnose issues without cluttering log folders. Optional screencast recording can be enabled separately, helping teams capture richer failure evidence when needed while avoiding slower default test runs.

Actually screenshots and screencasts are enabled when a '--logfile' argument is given on Odoo cli.
This behavior is not practical as it force developers to some CLI gymnastics (e.g. with tails) if they want to monitor logs in real time.

Also, this behavior is not obvious and people that use the '--logfile' parameter are not always aware that it could produce screenshots and screencasts in the same directory.

Finally, the runbot does not use the '--logfile' CLI arg and thus cannot benefit of them.

Proposal
=======
Screenshots and screencasts that are taken when a test fails are not something that we want to keep for a long period of time (even less when you are not aware of that behavior).

For those reasons, they should go in a temporary directory.
For example in '/tmp/odoo_tests/db_name/screenshots' and '/tmp/odoo_tests/db_name/screencasts'

That way, screenshots can be enabled by default without polluting the file system in the background.
On the runbot, a simple symlink in the Docker container can be used help them survive the container destruction.

Screencasts
-----------------

Problems:

* Tests that are using browser_js are really slowed down (up to 40% slower)
* ffmpeg have to be installed on the system

For those reasons, it should not be enabled by default.
Here are 3 different solutions:
1) Keep the old '--logfile' behavior for screencasts (not consistent with screenshots)
2) Use a new CLI arg '--screencast' to enable them
3) Use an 'ODOO_SCREENCAST' environment variable

Unpublished eLearning course cards are now shown with a slightly translucent appearance and an “unpublished” label. This makes it easier for website editors and designers to spot course publication status while working on the frontend.

The unpublished courses card are now a little bit translucid
and there is a 'unpublished' tag to clearly show their state


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

The online shop category experience has been optimized so category lists and search results load faster, especially for stores with many products. Messages shown when no products are found are also clearer, and category expand controls now better reflect what shoppers can actually open.

rebase-ff

Search panels can now be used in all multi-record views instead of only kanban views, making it easier for users to filter and navigate records consistently. HR and Lunch screens were updated to use this shared behavior, and related stability and usability improvements were added.

*base,hr,lunch

From now on, search panels can be activated on any multi-record views, and are no longer
restricted to kanban views.

The arch of the search panel has to be specified in the search view.

HR and lunch usecases have been adapted accordingly.

Task 1985921

eLearning users can now share a lesson while staying in fullscreen mode, without leaving the viewing experience to find the share option. This makes it easier to promote course content and reduces interruptions for learners and instructors.

A share button has been added to the fullscreen view to avoid
exiting the view to access the share tab on the full description
of the slide.

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

Child contacts are now automatically assigned to the same company as their parent contact, and the company field is locked when a parent is set. This prevents multi-company access errors when users communicate or log messages on related contacts.

Task : https://www.odoo.com/web?debug=true#id=1934813&action=333&active_id=131&model=project.task&view_type=form&menu_id=4720

Pad : https://pad.odoo.com/p/r.f3fd084c47d4f33cf0e31f9edbcda630

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

Course publishers can now see which lessons are available as free previews directly from the eLearning slide list. They can turn preview access on or off from the same page, making course management faster and clearer.

Users can now stop following a document from the chatter with one click, without seeing an extra confirmation popup. This streamlines a common action while still keeping confirmation when removing another person as a follower.

before this commit:
when user click on unfollow in chatter, it asks for confirmation to unfollow

after this commit:
when user click on unfollow in chatter, it will be unfollowed from particular
document straight away without any confirmation

Description of the issue/feature this PR addresses:
Do not show the confirmation popup while clicking on "Following" CTA in the chatter. 

Current behavior before PR:
the confirmation popup is showing while clicking on "Following" CTA in the chatter. 

Desired behavior after PR is merged:
when user click on unfollow in chatter, it will be unfollowed without any confirmation

Task:
https://www.odoo.com/web#id=1998188&action=327&model=project.task&view_type=form&menu_id=4720

Pad:
https://pad.odoo.com/p/r.b6ffbe3362a2d988a1989da79d03dcf6

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

The search panel is now supported consistently across multi-record views such as Documents, dashboards, Gantt, grid, map, and cohort views. This makes filtering and navigating records more uniform for users across different Odoo apps and reporting screens.

*documents,web_cohort,web_dashboard,web_enterprise,web_gantt,web_grid,web_map,web_studio

This PR is the counterpart of odoo/odoo#34219

Task 1985921

The rental configuration flow now uses a clearer date range picker, making it easier for users to choose rental periods. Odoo Studio was also updated so this date range field can be configured consistently when customizing views.

* Task: https://www.odoo.com/web#id=1936721&action=327&model=project.task&view_type=form&menu_id=4720
* Pad: https://pad.odoo.com/p/r.d4e99a626c897df13b055d9ed20177c4