A space between the category page and the main footer when applying specific settings

[wd7080]

Preconditions

1. Magento 2.2.1

Steps to reproduce

1. Go to Content -> Blocks
2. Add new block
3. Block information:
   a. Enable block -> Yes
   b. Block title: Contact Us menu
   c. Identifier: contactusmenu
   d. Store View: All Store Views
   e. I am trying to create a contact us form on a cetegory page. I added the following content to the static block editor:
   <p>{{block class="Magento\Contact\Block\ContactForm" template="Magento_Contact::form.phtml"}}</p>

<hr />
<p style="text-align: justify;">Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type and scrambled it to make a type specimen book. It has survived not only five centuries, but also the leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with the release of Letraset sheets containing Lorem Ipsum passages, and more recently with desktop publishing software like Aldus PageMaker including versions of Lorem Ipsum.</p>

4. Now go to Catalog -> Categories
5. Select the Default Category then -> Click on Add Subcategory
6. Category settings are as follows:
   a. Enable Category -> Yes
   b. Include in Menu -> Yes
   c. Category name -> Contac Us
   d. Content -> Add CMS Block -> Contact Us Menu
   e. Display Settings -> Display Mode -> Static block only
   f. Display Settings -> Anchor -> No
   g. Search engine optimization -> URL Key -> Contact
   h. Design -> Use Parent Category Settings -> No
   i. Design ->Theme -> Magento Luma
   j. Design ->layout -> 1 column
   k. Design ->layout update XML -> Empty
   l. Design ->apply design to the products -> No
   M. Click Save.

Expected result

1. You can view the contact us page in the menu

Actual result

1. There is a space between the content and the footer. See the image below.
   

2. The HTML content of this column is:

<div class="column main"><input name="form_key" type="hidden" value="sEXSrkYUlSkpqe2v"><div id="authenticationPopup" data-bind="scope:'authenticationPopup'" style="display: none;">
    <script>
        window.authenticationPopup = {"autocomplete":"off","customerRegisterUrl":"http:\/\/domain.com\/customer\/account\/create\/","customerForgotPasswordUrl":"http:\/\/domain.com\/customer\/account\/forgotpassword\/","baseUrl":"http:\/\/domain.com\/"};
    </script>
    <!-- ko template: getTemplate() -->
<!-- /ko -->
</div>

3. After the settings I've applied to the category page, this column must be hidden with zero space.
4. Complete image to the page:
   

[wd7080]

@magento-engcom-team were you able to reproduce this? Do you need an update?

[wd7080]

Guys, this is really a bug, the main column does not get hidden. Just look into this, please.

[wd7080]

Any update on this bug?

[magento-engcom-team]

@wd7080, thank you for your report.
We've created internal ticket(s) MAGETWO-85276 to track progress on the issue.

[sanjay-wagento]

Hi @magento-engcom-team, @okorshenko
I investigated this issue and working on it.
Please assign to me.
Thanks!

[magento-team]

Hi @wd7080. Thank you for your report.
The issue has been fixed in #13026 by @sanjay-wagento in 2.2-develop branch
Related commit(s):

• 023fb1a
• 7727086

The fix will be available with the upcoming patch release.

[okorshenko]

Hi @wd7080. Thank you for your report.
The issue has been fixed in magento-engcom/magento2ce#1325 by @magento-engcom-team in 2.3-develop branch
Related commit(s):

• e84cb3e
• 742819b
• cc2b11f
• ae8b187
• 35b3c02
• eae8936
• 90e4923
• b098dbc
• e8e4cdd
• 058e5e5
• 9368d5d
• bf19409
• a15ec34
• 9e4ce76
• 0995681
• 6772a2d
• b0d6bfc
• b037357
• 8de5951

The fix will be available with the upcoming 2.3.0 release.

[wd7080]

Hello
This has not yet been fixed in 2.3.0. I still have the same problem. I really waited for so long for this update to fix this problem. Disappointed!

[magento-engcom-team]

Hi @wd7080. Thank you for your report.
The issue has been fixed in #15726 by @sanjay-wagento in 2.3-develop branch
Related commit(s):

• ce176d2ab2ae16790f84c7d6836afb51b4d9060a

The fix will be available with the upcoming 2.3.0 release.

[sidolov]

Hi @wd7080. Thank you for your report.
The issue has been fixed in #15727 by @sanjay-wagento in 2.1-develop branch
Related commit(s):

• 5e6abd502f500d50cdde91af6c97dfc6f6dc861f

The fix will be available with the upcoming 2.1.15 release.

[philgschmidt]

Still seeing this problem in 2.3.3
What am I missing?