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 block type "promo-features-block" experiences a width-related issue when SSR is utilized with the configuration ssrConfig = {isServer: true}. Specifically, the width of the items within this block remains at 33% across all screen sizes, neglecting responsive behavior.
Expected Behavior
On smaller (mobile) screens, the width of each item within the "promo-features-block" should adjust to 100% to accommodate responsive design principles.
Current Behavior
When SSR is enabled (ssrConfig = {isServer: true}), the width of the items persists at 33%, even on smaller screens, counteracting mobile-responsive functionality. When SSR mode is disabled or not used, the rendering on small screens appears as expected, adhering to the 100% width for item divs.
Steps to Reproduce
Enable SSR with the configuration ssrConfig = {isServer: true}.
Observe the "promo-features-block" on various screen sizes.
Note the persisting width of 33% for item divs on smaller screens, rather than the expected 100%.
Possible Solution
A preliminary assessment does not suggest an immediate solution and requires further investigation into how SSR, or the specific isServer: true configuration, is impacting the responsive CSS or JS logic.
Description
The block type "promo-features-block" experiences a width-related issue when SSR is utilized with the configuration ssrConfig = {isServer: true}. Specifically, the width of the items within this block remains at 33% across all screen sizes, neglecting responsive behavior.
Expected Behavior
On smaller (mobile) screens, the width of each item within the "promo-features-block" should adjust to 100% to accommodate responsive design principles.
Current Behavior
When SSR is enabled (ssrConfig = {isServer: true}), the width of the items persists at 33%, even on smaller screens, counteracting mobile-responsive functionality. When SSR mode is disabled or not used, the rendering on small screens appears as expected, adhering to the 100% width for item divs.
Steps to Reproduce
Enable SSR with the configuration ssrConfig = {isServer: true}.
Observe the "promo-features-block" on various screen sizes.
Note the persisting width of 33% for item divs on smaller screens, rather than the expected 100%.
Possible Solution
A preliminary assessment does not suggest an immediate solution and requires further investigation into how SSR, or the specific isServer: true configuration, is impacting the responsive CSS or JS logic.
Context (Environment)
Browser: [e.g., Chrome, Safari, etc.]
OS: [e.g., iOS, Windows, etc.]
Screen Sizes: Small (Mobile) screens
Detailed Visuals
Without SSR (Correct Behavior):
![oie_7211815oHrQZbFE](https://private-user-images.githubusercontent.com/61822896/273405146-1c58db0a-b3de-489f-94e6-30a8a43334d5.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwOTQ3MDYsIm5iZiI6MTczOTA5NDQwNiwicGF0aCI6Ii82MTgyMjg5Ni8yNzM0MDUxNDYtMWM1OGRiMGEtYjNkZS00ODlmLTk0ZTYtMzBhOGE0MzMzNGQ1LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDA5NDY0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWE3YWM4YzlkNDlhMDkxODc4N2VjNmNlNDYzZjRhZDRiNGZhZWRhZTU0OWY3MDkxMWZjODNiMjA0ODdhYmI0YTImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.hVXjT5u0jkri9SC4MoxnF5hbk8XQD5OXuf2gaPZEv6Y)
With SSR (Incorrect Behavior):
![oie_7211729g6Vk5Fkh](https://private-user-images.githubusercontent.com/61822896/273405165-62097bd0-5fc3-450a-92d6-fe31040ec76d.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwOTQ3MDYsIm5iZiI6MTczOTA5NDQwNiwicGF0aCI6Ii82MTgyMjg5Ni8yNzM0MDUxNjUtNjIwOTdiZDAtNWZjMy00NTBhLTkyZDYtZmUzMTA0MGVjNzZkLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMDklMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjA5VDA5NDY0NlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE2Y2E4Mzk0ZTM4MTc5OTIxZGI0NzQ0ZDMxOWZjZGY4MTE3MTQwMDEzMjA4MjhiMWYyZTUwMDE0NzYwNzM0ZTAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.OlAGsc9x7rMq3Pd86NE76yXO2KP4nWvk8SWh6eGhZW0)
The text was updated successfully, but these errors were encountered: