Friday, June 7, 2024
2 changes · saas-17.1
Resolved issues and error corrections
Fixed an issue in the Indian localization where choosing an HSN code from autocomplete with the keyboard could leave the typed text in the field instead of the selected code. This makes data entry more reliable for users entering tax and product classification details.
Original PR description
prior this PR, when a user selects an option from the HSN autocomplete widget using the keyboard, the selected value is not reflected in the input field. Technical Reason: The `onSelect()` method in the HSN autocomplete widget calls `this.props.record.update()`, followed by a call to `commitChanges()` in `input_field_hook.js` due to the `keydown` event. Consequently, the update method is called twice: first with the selected option value and then with the user's typed input value. This sequence results in the input field displaying the typed value instead of the selected option. With this PR, selecting an option from the HSN autocomplete widget using the keyboard correctly updates the input field with the selected value. task-3961406
Recent messages in Discuss are now ordered consistently when messages have similar timing. This helps users see the expected latest message and reduces confusion in conversations.
Original PR description
Similar code than already adapted in 17.2. runbot-66529