This is really about Layout Builder and layouts that are defined by a module. In this case I'm using Layout Discovery to make this example simple.
So I am building a page using Layout Builder and I have selected a layout (provided by the Layout Discovery module) for a section. Now I'd like to add a field to the layouts configuration form (the form where I can select column widths and set administrative title). Maybe I'd like to add something like a background color picker or a text field for an extra class or whatever.
We try to migrate all of our Drupal WebSites from an on-premis infrastructure to Azure WebApp, all of the settings, deployment script are functional but during the test period we experienced a lot of latency mainly on backend (for example sometime it takes more than 30sec to be logged on the backend).
All the pages on the backend are really slow to be loaded.
We use an Azure for MariaDB instance with the same setting as on-prem.
I'm using we_megamenu. If I only define a one level menu everything works fine. But If I define a bigger menu with e.g. two 1st level rows there is a problem. If a menu entry from 1st level in 2nd row has subentries and I click on a 1st level menu button from 1st row, then the 2nd level submenu opens behind the 1st level button from row 2.