Search
Navigate
Branch
Sunday, January 19, 2025
6 changes
3 changes
Miscellaneous changes
The name search on the account field (account.account on account move line) looks for frequently used accounts for the partner. When no search text is provided, the name search suggests accounts that were previously used. When there are no frequent accounts, the name search returns nothing. To reproduce - create a vendor bill - select a partner that has never been billed - add a line - click the account many2one field dropdown Since no account options are available, the dropdown flas
Original PR description
The name search on the account field (account.account on account move line) looks for frequently used accounts for the partner. When no search text is provided, the name search suggests accounts that were previously used. When there are no frequent accounts, the name search returns nothing. To reproduce - create a vendor bill - select a partner that has never been billed - add a line - click the account many2one field dropdown Since no account options are available, the dropdown flashes open and quickly disappears. Forward-Port-Of: odoo/odoo#193999
Before this commit, when opening a channel on mobile the composer gets automatically focused. This is not a problem on desktop, but when on mobile it triggers the opening of the system keyboard, occupying half the screen and requiring a "back" command to close it. This happens because the function that opens the chat window will put focus on the composer. This commit fixes the issue by only focusing the composer when not on mobile. task-4115728 Forward-Port-Of: odoo/odoo#194122
Original PR description
Before this commit, when opening a channel on mobile the composer gets automatically focused. This is not a problem on desktop, but when on mobile it triggers the opening of the system keyboard, occupying half the screen and requiring a "back" command to close it. This happens because the function that opens the chat window will put focus on the composer. This commit fixes the issue by only focusing the composer when not on mobile. task-4115728 Forward-Port-Of: odoo/odoo#194122
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 th
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 Forward-Port-Of: odoo/odoo#194103
1 change
Miscellaneous changes
The tour fails as it splits a wrong shift and the last shift can't be split, you can have a look at screenshot in failed builds. Fixed the order of pills to be checked. task-4491233 Forward-Port-Of: odoo/enterprise#77326
Original PR description
The tour fails as it splits a wrong shift and the last shift can't be split, you can have a look at screenshot in failed builds. Fixed the order of pills to be checked. task-4491233 Forward-Port-Of: odoo/enterprise#77326
2 changes
Resolved issues and error corrections
Fixed an issue where text written in a full message composer could be incorrectly restored into another open chat draft. This prevents accidental message mix-ups when users work across multiple conversations or chatter windows.
Original PR description
Before this commit, when some conversations were open in chat windows and the full composer was open in a chatter, the content of full composer message composition could be duplicated in other…
Before this commit, when some conversations were open in chat windows and the full composer was open in a chatter, the content of full composer message composition could be duplicated in other conversation composers. Steps to reproduce: - open a discuss conversation in chat window - open a form view with chatter - quickly perform these actions in a 5 seconds window: - type something in composer of discuss chat window - clear content in composer of discuss chat window - open basic composer of chatter then type something - open the full composer - wait about 5 seconds, then open a new browser tab with the same URL => the chat window of discuss conversation contains the full composer text content This happens because when some content is typed in the non-full composer, the text content is regularly saved in local storage so that content is not lost on page reload. The saving is debounced 5 seconds whenever the user types something. The full composer must also be saved & restored in chatter, as this is also a frequent point of typing long messages and content may be lost without the save & restore feature. The code to handling it was poorly written and forgot to assume there could be more than 1 composer open at once: whenever a save content in composer is in progress, it was simply checking whether a full composer is open, and if so it was simply saving the full composer content. This explains the problem in the scenario above: when typing in discuss conversation in chat window, the save content is triggered after 5 seconds. The opening of full composer disrupts the discuss conversation composer content saving by not saving the discuss conversation composer but instead the full composer content in it. This commit fixes the issue by enforcing debounce saving to save the content in the current composer. The full composer was never intended to be implied in the debounced save content, only the basic composer is. The full composer saving content works differently: whenever the full composer is closed in non-discard way the save of full composer in basic composer must happen. Task-4485021 
Miscellaneous changes
Since odoo/odoo#191886, "download handlers" is available through "Update" page. As Windows IoT Boxes have no access to this page, the feature was unreachable. This commit fixes this behaviour by allowing access to Update page and disabling Linux specific tools on it. Forward-Port-Of: odoo/odoo#194145
Original PR description
Since odoo/odoo#191886, "download handlers" is available through "Update" page. As Windows IoT Boxes have no access to this page, the feature was unreachable. This commit fixes this behaviour by allowing access to Update page and disabling Linux specific tools on it. Forward-Port-Of: odoo/odoo#194145