Vertical position problem with theme Olivero: block diplay depends on the user role

Hi, the given information is not enough to reproduce this issue. I've tested it with different user roles and it seems working fine. Please provide the steps to reproduce this issue with screenshots. So, that it can be replicate easily.

Hi @Moni_10. Here some elements. May be not enough. Two blocs in the footer. The first one is from Drupal: olivero_powered. The second one is created with a view. With one field of type custom text. With the two images *A0 the problem can be seen: the height difference. Seems a detail, but annoying. The image *A1 shows what may be a key element: the difference between the two roles used. One is a basic role. The other is administrator, with the editing functionality shown in image *A1. This functionality doesn't exists for the other role. The presence or the absence of this correspond to different css configurations that create the problem. The goal of the change is to get some thing not depending on the role.

We already have position: absolute; on contextual class and on contextual class is added on div[data-contextual-id]

@Gauravvvv, same observation than you about contextual, but only for an administrator role. For a non administrator role such a contextual is missing. And it causes the problem. May be you prefer some thing specific to the default case.

In case of administration, we already have contextual which have position: absolute;. And for other user when contextual is not available, [data-contextual-id] is also not present, so no use of adding position: absolute;

@Gauravvvv, I want to say that position: absolute; is needed for other user too. I think.

For a better answer, as it can be seen on the image, in the case of non administrator role, class contextual-region and attribute data-contextual-id exist for the element. But may be it is a particular case.

I'm unable to reproduce the issue. I have followed the provided steps, and there is already a "position: absolute" property in place. I've also tested it with different roles and added a screenshot.

@nilesh.k, I try to understand why you don't get the same result than us. Verified again: same problem for us. Our html codes compared, between administrator an non administrator roles: the root difference is instruction class="contextual": only when it is okay. In your example class="contextual" is here, and the css is called (in our case it is the file core/modules/contextual/css/contextual.theme.css). To which role corresponds your example? For non administrator role do you really have the class="contextual"? We don't.