Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0057128Openbravo ERPA. Platformpublic2024-11-15 16:562024-11-20 14:33
Reportershuehner 
Assigned ToTriage Platform Base 
PrioritynormalSeverityminorReproducibilityhave not tried
StatusnewResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browserGoogle Chrome
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0057128: HTML ComboBoxes in backoffice with empty (default) value are no longer working in Chrome 131
DescriptionUsing latest Chrome 131 shows broken UI for some backoffice combo-boxes.

If an HTML ComboBox has a empty value (i.e. for default) instead of showing this empty value a selected element + also in the list of values when using latest chrome instead it shows a 'non existing' value which is 'concatenated test of all later combo entries'.

That is reproducible only on:
- Chrome version 131 (131.0.6778.69) latest stable release

It is NOT reproducible
- on Chrome version 130
- on Firefox

It seems to affect:
- HTML ComboBoxes as created by xmlEngine
- when used in old-style manual HTML reports

Steps To ReproduceLogin to backoffice (i.e. latest master in livebuilds)
Open the "Sales dimensional Report"
Look at the ComboBoxes:
- Business Partner Category
- Warehouse
- Product Category
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
has duplicate defect 0057167 closed Triage Omni OMS Issue in Sales Invoice Dimensional Report with the Latest Version of Chrome (131) 
Attached Filespng 57128-example-bad-chrome131.png (67,013) 2024-11-15 16:58
https://issues.openbravo.com/file_download.php?file_id=20493&type=bug
png

png 57128-example-good-chrome130.png (57,561) 2024-11-15 16:58
https://issues.openbravo.com/file_download.php?file_id=20494&type=bug
png

png 57128-example-good-firefox-132.png (24,288) 2024-11-15 16:58
https://issues.openbravo.com/file_download.php?file_id=20495&type=bug
png

png 57128-chrome130-warning.png (18,217) 2024-11-15 17:07
https://issues.openbravo.com/file_download.php?file_id=20496&type=bug
png

png Chrome 131.png (198,410) 2024-11-19 18:56
https://issues.openbravo.com/file_download.php?file_id=20524&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2024-11-15 16:56shuehnerNew Issue
2024-11-15 16:56shuehnerAssigned To => Triage Platform Base
2024-11-15 16:56shuehnerWeb browser => Google Chrome
2024-11-15 16:56shuehnerModules => Core
2024-11-15 16:56shuehnerTriggers an Emergency Pack => No
2024-11-15 16:58shuehnerFile Added: 57128-example-bad-chrome131.png
2024-11-15 16:58shuehnerFile Added: 57128-example-good-chrome130.png
2024-11-15 16:58shuehnerFile Added: 57128-example-good-firefox-132.png
2024-11-15 17:07shuehnerFile Added: 57128-chrome130-warning.png
2024-11-15 17:10shuehnerNote Added: 0172059
2024-11-18 07:33hgbotNote Added: 0172129
2024-11-19 11:26PracticsIssue Monitored: Practics
2024-11-19 12:11ffourcadeRelationship addedhas duplicate 0057167
2024-11-19 13:33eugeniIssue Monitored: eugeni
2024-11-19 17:50eugeniNote Added: 0172249
2024-11-19 18:11shuehnerNote Added: 0172250
2024-11-19 18:55eugeniNote Added: 0172251
2024-11-19 18:56eugeniFile Added: Chrome 131.png
2024-11-19 20:30PracticsNote Added: 0172252
2024-11-19 21:18shuehnerNote Added: 0172253
2024-11-19 21:39eugeniNote Added: 0172254
2024-11-20 14:33shuehnerWeb browserGoogle Chrome => Google Chrome
2024-11-20 14:33shuehnerNote Added: 0172358
2024-11-20 14:33shuehnerSeveritycritical => minor

Notes
(0172059)
shuehner   
2024-11-15 17:10   
Checking Chrome release info for 131
https://developer.chrome.com/blog/new-in-chrome-131 [^]

Might be side-effect of this change:
https://developer.chrome.com/release-notes/131#select_parser_relaxation [^]

Also see warning shown when using older chrome130 version about structure of the values in the select tag.

Manually editing html in devtools to remove those (extra divs, extra span, simple list of 'option') tags seems to avoid the problem.

Note:
Those div+span are likely present + addded either by or using xmlEngine template engine for those old-style html reports.
(0172129)
hgbot   
2024-11-18 07:33   
Merge Request created: https://gitlab.com/openbravo/product/openbravo/-/merge_requests/1445 [^]
(0172249)
eugeni   
2024-11-19 17:50   
Hello, seems a problem with Chrome 131.0.6778.69. New 131.0.6778.70 apparently solves that problem

Hope it helps,
Eugeni
(0172250)
shuehner   
2024-11-19 18:11   
Hi Eugeni,
if that get's confirmed that would be very helpful :)

On Linux (Ubuntu) with the official chrome deb repo i only see .69 available.
And reading here: https://chromereleases.googleblog.com/2024/11/stable-channel-update-for-desktop_12.html [^]
Sounds like same first stable release is tagged .69 on linux but .70 on Mac.

Could you detail a bit more the environment (i.e. OS) where you've seen that fixed?
(0172251)
eugeni   
2024-11-19 18:55   
Hi! Chrome for Windows

Attached image. A couple of customers confirmed it is working fine again, so it seems something was wrong with 131.0.6778.69

Best,
Eugeni
(0172252)
Practics   
2024-11-19 20:30   
Hi! I confirm the same as Eugeni says. On Windows with the latest version of Chrome it works fine.

Hector Camps
(0172253)
shuehner   
2024-11-19 21:18   
Hello,
by now on Ubuntu Linux there's also a chrome update available (131.0.6778.85). Using that version i also see this problem fixed :)

Thank you Eugeni and Hector for letting us know and confirming it works on your end.
(0172254)
eugeni   
2024-11-19 21:39   
You are welcome, Stefan!
(0172358)
shuehner   
2024-11-20 14:33   
Downgrading issue from critical to minor as the functional/impact of it has been fixed by browser update (see previous notes).

But keeping the issue open to still look into the html tag nesting topic (see attached merge request). See also related https://openbravo.atlassian.net/browse/RM-19166 [^] which is to look into the chrome130 warnings (which now have re-appeared with the chrome131 minor version fixing the functional problem).