What is the bug or the crash?

Not crash, even not really a bug, but annoying UX for cases such:

If a NetCDF file has lo-o-o-ong 'description' of a variable in metadata, the long text is then used for 'BAND' description drop-down and consequently influence the behavior of the other objects in the Layer properties dialog. I need to resize the DIALOG to an inappropriate size to see all its objects (see snapshots attached) and work with layer style. If the description is longer than my screen, the DIALOG is not usable at all, some objects just do not fit into the screen and horizontal scroll-bar must be used (which is not great UX)

The same behavior is with GeoTIFF files which have some specific metadata included (example of such file attached).

Some NetCDF files are handelled better, (e.g. files with 'time' dimension - 'units' are preferred to 'description').

Screenshots
Layer properties dialog with long BAND description (horizontal scrollbar must be used to access all features of the DIALOG)

Docked layer properties dialog with long BAND description (horizontal scrollbar must be used to access all features of the docked DIALOG)

I need to dramatically resize Layer properties DOCKED dialog to see all tools in the GUI (without a need of horizontal scrolling)

Possible fixes

• Truncating long BAND texts to reasonable length
• Preferrably using 'long_name' metadata attribute (instead of 'description')
• Let the user select/customize what is the description for BAND
• other?

Steps to reproduce the issue

• Upload the provided NetCDF or/and GeoTIFF file in the
• Select the file and open Layer properties dialog (docked or normal)
• You should now notice the long text for BAND drop-down menu, some of styling tools might be over the edges of the dialog window; horizontal scroll-bar must be used (which is bad for UX)

TEST-files-NetCDF-GeoTIFF.zip

Versions

QGIS version
3.34.15-Prizren
QGIS code revision
386f258
Qt version
5.15.3
Python version
3.10.12

OS version
Ubuntu 22.04.5 LTS

Supported QGIS version

• I'm running a supported QGIS version according to the roadmap.

New profile

• I tried with a new QGIS profile

Additional context

I experience this UX issue in QGIS for a long time, many previous versions. Fixing the issue would certainly help the UX.