Magento2: System Messages Block in Admin panel is annoying.

[ytorbyk]

Magento 2.2.0-dev

The System Messages Block moves the page down when it appears. It is annoying such as it happens on each page.
It is not always possible to perform suggested actions, so the messages appear and shift page in 1-2s after it's loaded.

Is it possible to change this behavior?
For example, show amount of messages without shifting a whole page?

Thanks!

[magento-engcom-team]

@ytorbyk thank you for your report.
Please use the issue reporting guidelines to report an issue. Please, edit issue description and include the preconditions, the steps required to reproduce, the actual result, and the expected result.
Please, add the following information:

• [ ] Preconditions: Magento version
• [ ] Steps to reproduce
• [ ] Expected result
• [ ] Actual result

[magento-engcom-team]

Hi @ytorbyk
The best way to address the issue is to create a pull request. You are very experienced Magento 2 developer, so you can help us with this issue. We are looking for pull request from you 👍

[vapopov]

[magento-engcom-team]

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

[orbitrod]

Until a proper fix can be rolled out, I created a userscript to fix this problem using Tampermonkey. For those that do not know what Tampermonkey is, it is a userscript manager browser extension, that allows users to install scripts that make on-the-fly changes to web page content after or before the page is loaded in the browser.

Here is the script
https://github.com/EnochDataSystems/gists/blob/master/magento2-system_messages-fix.js

The script will reduce the width of the systemMessageBlock and move it to the top left corner. When the systemMessageBlock is loaded, it will hover over any text or elements in that corner, but after 5 seconds it will fade away.

This is an easy quick fix and doesn't involve touching the Magento code.

[magento-engcom-team]

@ytorbyk, thank you for your report.

Unfortunately, we are archiving this ticket now as it did not get much attention from both Magento Community and Core developers for an extended period. This is done in an effort to create a quality, community-driven backlog which will allow us to allocate the required attention more easily.

Please feel free to comment, reopen or create new ticket according to the Issue reporting guidelines
if you are still facing this issue on the latest 2.4-develop branch. Thank you for collaboration.