Fixing - Responsive Layout on footer

[rodrigoobiassi]

I was showing the platform to a prospective client and noticed this problem. Broken responsive layout.

1 -

2 -

[magento-engcom-team]

Hi @rodrigoobiassi. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento-engcom-team give me test instance - deploy test instance based on PR changes
• @magento-engcom-team give me {$VERSION} instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

[magento-cicd2]

All committers have signed the CLA.

[magento-engcom-team]

@rodrigoobiassi thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

[gwharton]

Please check if PR #17006 fixes this for you and close as necessary.

[sidolov]

@rodrigoobiassi , please, check comment above and take a look at merge conflict.
Thank you!

[rodrigoobiassi]

Hi @sidolov, I just made the requested change. Thanks.

[gwharton]

@rodrigoobiassi Are you sure this PR is still required. PR #17006 made changes to the responsive layout for mobile devices, namely it made the mobile screens behave the same way as the desktop screens with respect to the footers. i.e that if the page/content is shorter than the screen, then the footer snaps to the bottom whereas if the page/content is longer than the screen, then the footer is pushed to the bottom of the content, and not the bottom of the screen.

It looks like this PR is in conflict with this resolution, i.e that it will cause the footer to always snap to the bottom of the screen regardless of the page/content size. This is not consistent with the desktop layout.

[sidolov]

Hi @rodrigoobiassi , please, read the comment from @gwharton , maybe the issue resolved and we can close this pr?

[sidolov]

Hi @rodrigoobiassi , I am closing this PR now due to inactivity.
Please reopen and update if you wish to continue.
Thank you for the collaboration!