[guy_bParticipant]

Hi guys,

I guess this is not particularly important, and I know you have a big day today with the new release etc, but something to put on the backburner for a minor update in the future.

Right now, we have:

.x-logobar → z-index: 1030

.x-topbar → z-index: 1031

.x-widgetbar → z-index: 1032

This is a very narrow range in terms of stacking order, so if, for example, I want to put custom content into the Topbar and position it somewhere in the header, I have to change the z-index of one (or all) of the others by overriding it/them.

If I don’t, my custom content is either hidden, partially hidden, or shows up over the content in the top widget bar when it is expanded.

It would be much better if the z-index for these 3 elements were stacked a bit further apart, leaving some slots available for adding our own stacking order for custom content without needing to override the defaults as well.

Something like:

.x-logobar → z-index: 1030

.x-topbar → z-index: 1050

.x-widgetbar → z-index: 1070

…….or I guess you could add an option to the Customizer to set the z-index to whatever we want?

Thanks

Guy

[RadModerator]

Hi Guy,

Thanks for your suggestion and we will review your request 🙂

You can always use relative positioning for your container right before using z-index for your child elements. All elements inside the relative container will takes z-index restricted to that containers only.

Like any elements even with lower z-index or higher z-index will stay inside. So even if you add 1070 on your topbar content, while widget bar has 1031, your widget bar will still appear on top since the topbar container is 1030.

Thanks again!

[guy_bParticipant]

Thanks, however what you have suggested doesn’t work for the specific needs I have, which is why I mentioned it, and also why I had to override the defaults.

Anyway, as I said, not urgent, and just a heads-up that there are people who use frameworks slightly beyond the default build, so flexibility is a good thing, right?

Thanks for reading.

Guy

[RubinKeymaster]

Thank you for your feedback we will look into this and I will put it on our internal list.

[Author]

Posts