Elementor
Allow to wrap elements via Context-Menu, Custom class to body & Context-aware Custom CSS field #31485
Replies: 2 comments 2 replies
-
|
Hello @emuplugins! Thank you for sharing your ideas and suggestions! 🙏 1. Wrapping elements with Divs through the Context-MenuThis is a great idea, it could help streamline the workflow! Thank you for sharing it! 💪 2. Body ClassesI can see the use case for this type of feature, however, I'm not sure this falls into the scope of Elementor, since this is a very advanced developer-oriented request, and would fit better into a developer-customization workflow. For example, while you are enqueueing your custom scripts (which is the recommended way of adding scripts to WordPress), you could also use the 3. Context-aware Custom CSS fieldWe are still considering the best approach to include a Custom CSS field in atomic elements. Making it context-aware such as applying the correct breakpoints automatically, or going further and doing the same thing for Classes and States ( Thank you again for the feedback! Keep it coming! 🙌 |
Beta Was this translation helpful? Give feedback.
-
|
Hello @nicholaszein! 👋 First of all, the performance of the builder is so much better. Congratulations on that — it feels like water, I don't know... incredibly fast! About the CSS tab: I understand your point, but we use global breakpoints way more often than custom ones. Honestly, if I've used them more than four or five times in the past four years, that's already a lot... 🤔 I've been working with Elementor since my teenage years, and whenever I use the Custom CSS tab in Elementor, I have to follow the breakpoints set in the global settings. Now, imagine if it were already integrated with the global breakpoints — it would save us a lot of time. It would also organize the code much better since it wouldn't all stay cramped in the same tiny space, and the rules would only appear in their respective breakpoints. Here’s an example of how this could help optimize our workflow: 😊 2025-06-23.18-14-37.mp4There’s no problem when we write a tiny piece of code like this. But the problem comes when we need to write very specific rules for each breakpoint — things that aren’t possible directly in the editor, like advanced animations or more interactions. The CSS tab is small (which is fine), but writing too many lines of code in there makes it harder to understand our rules and what they do. |
Beta Was this translation helpful? Give feedback.
-
|
Hey @emuplugins! Just updating you here too. Have you seen the new Custom CSS field in the v3.33 Beta release? It does exactly what you were asking for! 🙌 We would love to hear your feedback about it! Your input really helped us on developing this feature! 💪 Best regards! |
Beta Was this translation helpful? Give feedback.
-
|
thankyou so much 👏📈 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Also, when the CSS tab is updated to V4 make it responsive, so that each breakpoint has its own CSS rules, inheriting the rules from the breakpoint above. This would avoid the need to use media queries and greatly improve usability and responsiveness.
It would be great if, when we right-click on an element, an option appears in the dropdown menu to wrap the element with a div. This is better than manually adding a div and dragging the element inside it.
Body Classes:Allow adding a custom class to the body. This will enhance the capabilities of what we can do with JavaScript. For example, we could remove a class once the fonts are loaded to hide our custom-built preloader.
Thank You 😊
Agreement
Beta Was this translation helpful? Give feedback.
All reactions