It would have been nice to get some warning or time to figure out what to do before it was shut off, sorry that is really not ok. the notice could have gone up days ago, not the moment it is changed, some of us learn as we go around here… that said
For those of us not so technically informed, could someone please explain how this is accomplished in detail, maybe a few photos, as I cannot get it to take display:none because of the ( : ) … thanks, as I do my mobile pages separately this is a bummer for me instead of 1 click, now its…
Any section that currently uses the visibility function will still use this until you make that section visible on all - then the notification is displayed and function removed.
Not much you can do there, but keep in mind it would be rare that an external viewer would load the site in a certain window size and the resize (not impossible but rare).
Alternatively, you could rework things so that this interaction would only trigger on the desktop and the object this interaction makes visible, is only visible on the desktop. So if someone loads the site in their desktop, triggers the interaction to make the object visible, but then resizes the screen to a smaller break point, the object will then been hidden as the new media queries take hold.
This is what I had been trying to do yesterday evening and for some reason the element that I only wanted to be visible on desktop also shows on the other break points once it has loaded (even though it is display:none for the others).
If you could take a look at fountech.ai - the .welcome div is visible (after resizing from desktop to mobile),
Some of us are using Webflow to earn money, and having your workflow disrupted suddenly without prior notice is just rude in my opinion. I also was building Mobile versions seperatley and having 1 button to do this was great, and now we must manually go thorugh all elements we want to adjust?
I understand the fact there were bugs, and you are trying to improve the product, but this is not the correct way to do things.
This scenario also buggy. You hide element X than you bring it back by “display: block” but the correct display in your design is “display: inline-block” or “display: flex”.
The main idea her - in “real life” you hide/show a lot of elements (In stage mode).
Give me option. If i dont use interaction-2 in project X i want “easier life”. This idea is not “panel feedback” - to force users to change the way they work for some bugs in animation (And to “kill” valid CSS property).
If someone hides element by the editor (visibilty hidden) and than try to show this element by interaction and other “wrong” planing of animations and base CSS mistakes - That’s his problem, not mine.
I too prefer buttons for regular display options and expand for advanced stuff.
Speed of use being a major asset for webflow, the heavy usage elements should stay visible and easily selectable.
I really loved the ‘display on device’ buttons, would love it if they didn’t go. We can use ‘display: none’ but this was so easy! Use them all the time for effects that would be lost on mobile or the other way round
I Agree, however after reading the thoughts in this post it was a sloppy / lazy solution. I think going forward it’s much better for everyone and will encourage better practice (but yes, it was very handy!).
For those of us who dont do this for a living and just make our own website, this wasted time looking for those buttons, trying to understand why I couldnt get them to appear anymore
