This functionality is being removed from the webflow designer UI so I'm creating a wishlist request to reinstate it:
Device Specific Element Visibility
It is highly useful to be able to stop an element from loading altogether on a particular device to save bloat desktop code and assets loading when they aren't required. This increases page load speed, eliminates duplicate content issues and improves SEO for mobile specific designs.
The css class Display: None continues to load the code and assets even if they are hidden in the viewport. Display: None is also difficult to apply across hidden classes with Webflow’s class system, and elements cannot be easily manipulated when hidden in the editor.
I propose the device specific element visibility functionality is reinstated and any bugs ironed out using the buttons previously available in the webflow designer UI.
Given that this functionality is available in the Designer by adding display styles on each breakpoint, we're not planning to add back a legacy feature which was unpredictable behavior.
Thank you for the response admin, however, "Unpredictable behaviour of a legacy feature" was caused by some bugs in newer versions of webflow that conflicted with an extremely useful feature, not from a lack of usefulness or technical obsolescence. The feature exists in numerous other platforms for good reason and in webflow, aids mobile page load times significantly by not loading contained assets.
The labelling of "legacy" shouldn't stand as a result of product management realising it's much less work forcing the use of display: none, than properly resolving a bug for optimal function and end-visitor optimisation. Similarly, marking this request as already exists doesn't meet the need here. I often find the absence of this functionality problematic/limiting for mobile design and now build around this limitation to the detriment of the end website product. In pursuit of optimal page performance and flexibility, the request makes clear the difference between using display: none, and dynamically not loading an element altogether for a particular break point. Please reconsider bringing this feature back up to date with the latest version as it adds a lot more to the product than most realise.
Thank you for your consideration
Attachments Open full size