0007671: Correct bootstrap Version Support still missing

ID	Project	Category	View Status	Date Submitted	Last Update

0007671	module Visual CMS	module Visual CMS - sub	public	2024-06-12 11:51	2024-06-14 15:57

Reporter	a.steinbach	Assigned To
Priority	high	Severity	minor	Reproducibility	always
Status	confirmed	Resolution	open
Product Version	5.0.1

Summary	0007671: Correct bootstrap Version Support still missing
Description	VCMS still uses Bootstrap 3 Breakpoints in the Admin Configuration overview, though Apex is running with Bootstrap 5. This causes 2 major issues: - The rendered VCMS Markup produces bugs in Frontend, because the Breakpoint classes have change since Bootstrap 3. See https://getbootstrap.com/docs/5.0/layout/breakpoints/ vs https://getbootstrap.com/docs/3.4/css/#grid - Bootstrap 4 has only 4 Breakpoints, while Bootstrap 5 has 6. You cannot use all available breakpoints this way
Additional Information	There is a Image attached with the current Layout of the widget design settings. There should be 6 Breakpoints to utilize Bootstrap correctly. The rendered classes in frontend are also wrong.
Tags	Admin, Apex, CSS
Attached Files	Bildschirmfoto 2024-06-12 um 11.45.59.png (63,291 bytes) Bildschirmfoto 2024-06-12 um 11.45.59.png (63,291 bytes)

QA 2024-06-12 19:14 administrator ~0017036	Please provide further information on how bugs in the frontend can be reproducible.

a.steinbach 2024-06-13 10:26 reporter ~0017041	As I mentioned above, the grid classes/breakpoint classes in Bootstrap 5 are vastly different from those in Bootstrap 3. The VCMS now apparently renders the correct classes for Bootstrap 5 if the theme is not Flow (which does not include all themes that inherit from Flow, but that should not bother us here), but simply sets two classes for the smallest breakpoint, namely "col" and "col-sm". So you can't really use the SM breakpoint. There is also no support for the XXL breakpoint. So there are no obvious bugs in the frontend, but you can't use Boostrap the way it's supposed to be used. Another problem is that the default viewport is the tablet view. This is not directly a bug, but it makes maintenance unnecessarily difficult. You should use either the smallest or the largest viewport to be able to work effectively within a theme.

QA 2024-06-14 15:55 administrator ~0017050	Thank you for your information. This topic is on our to-do list.