You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The very basic scenario for responsiveness is that you may need to have 6 columns in a row for desktop, but 3 for mobile. PageBuilder not only does not provide such possibility, but also hardcodes the width: 100% into style="". As a result, you cannot even make website elements responsive with CSS as the styles are being overriden.
Expected behavior (*)
The bootstrap-like classes should be used for definition of with / number of columns, as a result, you would be able to declare that you want to display X columns in desktop, Y columns in mobile version.
Also - there should be no width hardcoded in style="" attribute.
Benefits
PageBuilder would support basic responsiveness
Additional information
The text was updated successfully, but these errors were encountered:
The inline style problem has been solved in the scope of the #558. This improvement will be available in the next release which will be available in Magento 2.4.2 release. Along with these improvements we will post an article on devdocs how it works and how to use it. Thanks for your report.
Description (*)
The very basic scenario for responsiveness is that you may need to have 6 columns in a row for desktop, but 3 for mobile. PageBuilder not only does not provide such possibility, but also hardcodes the
width: 100%
intostyle=""
. As a result, you cannot even make website elements responsive with CSS as the styles are being overriden.Expected behavior (*)
The bootstrap-like classes should be used for definition of with / number of columns, as a result, you would be able to declare that you want to display X columns in desktop, Y columns in mobile version.
Also - there should be no
width
hardcoded instyle=""
attribute.Benefits
PageBuilder would support basic responsiveness
Additional information
The text was updated successfully, but these errors were encountered: