Sticky header floating under top when there is no buttons in the toolbar

[OleksiiBulba]

Preconditions (*)

1. Install Magento 2.3.1
2. Create module Vendor_Module

Steps to reproduce (*)

1. Create listing grid without this node:

<listing ...>
    <settings>
        <!--<buttons></buttons>-->
    </settings>
</listing>

2. Set this node value:

<listing ...>
    <listingToolbar>
        <settings>
            <sticky>true</sticky>
        </settings>
    </listingToolbar>
</listing>

3. Open admin grid page and scroll down for toolbar sticking to top

Expected result (*)

1. Toolbar sticks to top:
   

Actual result (*)

1. Toolbar sticks to 77px under the top
   

[m2-assistant]

Hi @OleksiiBulba. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

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

@OleksiiBulba do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[OleksiiBulba]

This issue related to #8455

[m2-assistant]

Hi @konarshankar07. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.
  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[konarshankar07]

Hello @OleksiiBulba
I've fixed this issue and updates are on #23247. Please test and let me know if you find any problem.

Thanks

[m2-assistant]

Hi @shikhamis11. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.3-develop branch

  Details

  - Add the comment @magento give me 2.3-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.3-develop branch, please, add the label Reproduced on 2.3.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Verify that the issue is reproducible on 2.2-develop branch.

  Details

  - Add the comment @magento give me 2.2-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.2-develop branch, please add the label Reproduced on 2.2.x

• 6. Add label Issue: Confirmed once verification is complete.

• 7. Make sure that automatic system confirms that report has been added to the backlog.

[shikhamis11]

Hello @OleksiiBulba
Thanks for your report
this issue seems to be duplicate of #22614 so closing this one

[magento-engcom-team]

Hi @OleksiiBulba. Thank you for your report.
The issue has been fixed in #23247 by @konarshankar07 in 2.3-develop branch
Related commit(s):

• ce56c70e90172d8cb936c12232bf66532ea8b32c
• f5a93b779a41a5cb14830814e553876ccb7cdbcb
• a3fa8d1e2cb5713c7071c0fa8997af57fe67a559

The fix will be available with the upcoming 2.3.3 release.