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