-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Theme styles issues #10501
Comments
Hi @dollhauss Thanks
|
Hi @shilo-ey Thanks for your reply.
To clarify - if you tick the Disable Default Colors and Disable Default Fonts options - the customizer fonts are not applied - Roboto is added globally instead. |
Point 2) is happening with me as well, I am just using Hello Elementor + Hello Theme Child. |
Came here to report #2 as well. The default line-height style of |
Same problem here. Theme style is wreaking havoc with my Astra settings. For example, I have different link colors for my primary menu than I do for my regular content. Elementor theme style is overriding that and now I can only have one link color on my site. It gets rid of my primary menu customization on desktop view. It still works on tablet and phone. Send help! :p |
I've come across same issue with Astra and other themes.
In this case, body.elementor-kit-16 selector overrides the color of theme in the header, footer and sidebar though I have not used Elementor widgets. In my opinion, Elememtor should not apply its CSS of Theme Style to the Theme's Header, Footer or Sidebar. Since there is no option for Site Title or Menu color in the Theme Style users are not able to change the color at all. Eg: https://share.getcloudapp.com/JrubkKvA Solution:
|
I just want to add, this is not specific to Astra Theme. This issue occurs with OceanWP, while settings in Theme Style override OceanWP settings, it fails to override |
I don't like using issue threads to complain about things, but in this case I really hope this gets fixed soon. It's such a fundamental feature of Elementor that is broken here, and I'm pretty surprised it's still unresolved. |
ref: #11036 fixes this issue |
@shilo-ey I've mentioned the same on the issue #10649 :
Could you pls reconsider this and remove it completely? Your solution probably fixes the problem with the Theme Styler but not the conflicts with the themes! I want my headers defined in the theme ONCE, without the need to re-defined them again in the Themer. |
The Theme Style feature allows you to set the base style rules for your site. If an element overrides this setting - just like in themes/CSS reset - it should override it. If we will remove this setting completely we can potentially affect existing sites. therefore we replaced the selector to be a more general one. |
@shilo-ey I know eactly what each part of WP allows me to do and what is the cascade flow of each change. The thing is, that Elementor's rule for line-height is breaking this flow! For no reason it sets the line height to 1em for all the header elements, no matter, what is defined in the theme or Customizer (and what is even worse, no matter what is the type of the element - header, paragraph, span, div, ...). This is a long time issue, it's been here since early 2018. Pls see the coment from @bainternet here: #3197 (comment) He said the very same line about the possible affection of the existing sites there. And he added that the solution would come with the Theme styler. Well the Styler is here now, but we still miss the solution. Please take this opportunity to solve it once for all. Possible solutions, without affecting the existing sites:
The point is, that Elementor shouldn't be so "Elementor-centric". Theme Styler is a nice addition for somebody, who don't want (or can't) use a theme or Customizer for defining the glogal styles. But then there are other people, who like to have their styles defined in the theme in one place and don't want to use your Styler (especially just for this one task only). For them it's a big complication. Thanks |
@black-eye @shilo-ey Perhaps the second solution could be rephrased, so it becomes a checkbox that has a label like "Enable legacy CSS", and then other old CSS rules can go in there over time. And put it somewhere out of the way like in a Troubleshooting tab since only a handful of users will need to know about it, as older ways are phased out. I really appreciate that Elementor devs are attempting to look after users whose sites would be affected with the removal of the rule. However it should also be balanced against the impact it has on new users, particularly when great new features are announced, which turn out to be broken by legacy support. So the idea of having a legacy CSS stylesheet that can be toggled on or off is a nice one. |
Please provide a hook to allow for disabling this and other features for people that want to remove this completely from the site. |
One more think to consider. There are themes, which try to resolve this 1px line-height issue in their settings. One example is Page Builder Framework. They have an extra rule which overrides Elementor's default setting, so Elementor pages match their theme & customizer settings. By this new rule you are breaking the backward compatibiliy with these themes (again). So the best way would be to remove the line-height property, doesn't matter how:
Whatever suits you best, but please resolve it. |
This issue has been resolved in Elementor v2.9.9 Feel free to update Thanks! |
Prerequisites
Description
Using Astra Pro
Theme Styles have a few issues:
Steps to reproduce
Try the above options with Astra Pro as the theme.
Isolating the problem
Environment
System Info
``` Cloudways, Vultr server ```The text was updated successfully, but these errors were encountered: