In core/utilities.css, .ease-container sets max-width: 1200px with padding-left: var(--ease-space-6) and padding-right: var(--ease-space-6). However on viewports that are exactly 1200px wide, the container fills 100% of the viewport but the padding-left and padding-right only apply when width: 100% is active — not when max-width: 1200px kicks in. This means at exactly 1200px viewport width, content touches the very edge of the screen with no breathing room because the internal padding is already part of the 1200px max-width calculation.
Steps to reproduce:
Set browser viewport to exactly 1200px wide.
Place content inside .ease-container.
Observe content sits flush against viewport edge with no visible padding.
Expected: The container should always maintain visible horizontal padding regardless of viewport width matching max-width.
Files affected: core/utilities.css
Labels: bug, component, GSSoC-26, gssoc:approved, level:intermediate
In core/utilities.css, .ease-container sets max-width: 1200px with padding-left: var(--ease-space-6) and padding-right: var(--ease-space-6). However on viewports that are exactly 1200px wide, the container fills 100% of the viewport but the padding-left and padding-right only apply when width: 100% is active — not when max-width: 1200px kicks in. This means at exactly 1200px viewport width, content touches the very edge of the screen with no breathing room because the internal padding is already part of the 1200px max-width calculation.
Steps to reproduce:
Set browser viewport to exactly 1200px wide.
Place content inside .ease-container.
Observe content sits flush against viewport edge with no visible padding.
Expected: The container should always maintain visible horizontal padding regardless of viewport width matching max-width.
Files affected: core/utilities.css
Labels: bug, component, GSSoC-26, gssoc:approved, level:intermediate