Friday, January 17, 2025
3 changes · 17.0
Resolved issues and error corrections
Studio no longer shows the option to add videos when editing HTML fields, because that capability is not supported in this context. This prevents users from selecting a setting that would not work as expected and reduces confusion during page or form customization.
Original PR description
**Problem**: Enabling the addition of videos from Studio is not supported. This option should be removed. **Steps to Reproduce**: 1. In Studio, focus on any HTML field. 2. Under "Properties," there should be no "videos" option. opw-4405801 --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr
Discuss calls now keep the small video preview stable when users share their screen and turn on their camera. This removes distracting flicker during call interactions, making meetings feel smoother and more professional.
Original PR description
Before this commit, during a discuss call while sharing screen and enabling camera, the inset card (= small video stream preview in bottom right of call view of the participant, either camera or screen-sharing depending on other stream being main active) was flickering. This happens because each rendering of the call view re-renders the inset, which leads to the perceived flickers from stream being re-rendered. The main cause of re-render comes from `setInset()` that is invoked whenever the `visibleMainCards` getter is called with inset, which is triggered on renderings like mouse-hovering on call view to display the call actions. Even when the inset card is unchanged, `setInset()` produces another object, which forces OWL to re-render the inset component. This commit fixes the issue by having `setInset` reusing the inset data object if the inset to render refers to the same inset session. Task-4484908
Fleet document centralization now automatically assigns the correct folder for every company, not just the main one. This prevents company-specific document settings from showing an enabled fleet option with no folder selected.
Original PR description
How to reproduce: - install stock and documents_fleet - go in the settings and chose the company "My company (Chicago)" - go to the Document settings "Centralize your Fleet' documents" is enabled but the folder is empty. This is because the fleet folder is not yet created when the ORM add the field "documents_fleet_folder" and that documents_fleet only set the folder for the main company. We solve the problem by setting the default folder in the post init hook for every company that has an empty folder. Task-4294237