# Trying to streamline using drop zones

**URL:** <https://forums.realmacsoftware.com/t/trying-to-streamline-using-drop-zones/45598>\
**Category:** Elements API\
**Created:** [December 12, 2024, 8:56pm UTC](https://forums.realmacsoftware.com/t/trying-to-streamline-using-drop-zones/45598 "2024-12-12T20:56:57Z")\
**Posts on this page:** 1\
**Showing post:** 72

<div class="post-metadata">

**Author:** ![ben](https://dub1.discourse-cdn.com/flex005/user_avatar/forums.realmacsoftware.com/ben/32/28488_2.png) [@ben](https://forums.realmacsoftware.com/u/ben)\
**Post date:** [January 9, 2025, 9:06am UTC](https://forums.realmacsoftware.com/t/trying-to-streamline-using-drop-zones/45598/72 "2025-01-09T09:06:15Z")

</div>

> [@upssjw](#):
>
> hidden stops you setting visible for any screen size above you cannot set visible at a higher screen resolution by clicking on the responsive dots, you can do this in normal tailwind

From what I can see in your video, this looks like a bug. I’ll have to investigate this one some more and see about getting a fix in an upcoming beta. It should “just work”, but isn’t for some reason 😅

> [@upssjw](#):
>
> if you do this in tailwind you can set the next screen as md:block

The `Visibility` setting in Elements is setting the `visibility` CSS property.

The `block` utility classes in Tailwind sets the `display` CSS property.

So I believe you might be confusing those two properties.

We don’t have a setting for the `display` CSS property in Elements due to various technical and/or user experience reasons.

Hope that clears things up! 🙂

---

_[View the full topic](https://forums.realmacsoftware.com/t/trying-to-streamline-using-drop-zones/45598)._