• Resolved Artan

    (@artankrasniqi1988)


    Hi,

    whoever of your developers thought this line of CSS would be a good idea should learn about CSS inheritance. Because it is causing massive conflicts with own styles and CSS. For example I have small transitions that are slightly visible and are set to work also on browsers set on reduced motion. Your CSS simply overwrites my styles because its specificity is extremely high.

    CSS found in your file “custom-frontend.min.css”:

    @media (prefers-reduced-motion:reduce) {
    .animated {
    animation:none!important
    }
    html * {
    transition-delay:0s!important;
    transition-duration:0s!important
    }
    }

    The specificity of your CSS

    html * {
    transition-delay:0s!important;
    transition-duration:0s!important
    }

    pretty much outmatches all CSS regarding transition delays and durations also because “!important” is set. On this level (select all elements “*”) you should really avoid this. You pretty much killed the CSS for all users regarding transition delays and durations who have set this for reduced motion and are overwriting all styles.

    So, please remove this line of CSS completely and do it on the html elements where you really need it or use specified classes for your elements where you want to use this instead of trying to force it globally for all elements coming after the html tag. Also the !important-declaration has to be gone. As a plugin developer you shouldn´t use this as it will always at some point create a conflict with the CSS of users.

    This is really not the way to go when u want to be a good developer so please fix this and contain it to only the need of your plugin.

    Thanks.

Viewing 11 replies - 1 through 11 (of 11 total)
  • Thread Starter Artan

    (@artankrasniqi1988)

    Please fix this fast, as it is overwriting so many parts of my website (and pretty sure of all your users). All my small animations are set to 0 which influences my site very badly.

    Plugin Support Milos

    (@miloss84)

    Hello there,

    Thank you for being so patient.

    I have taken a look at your query, since every question related to Elementor code and its inner functioning is best addressed with our developers.

    If you would like assistance with these kinds of issues, I advise you to visit our GitHub page on http://www.github.com/elementor and submit this query to our developers as they will be able to assist in the best possible way and/or give you advice on how this can be handled.

    Looking forward to hearing back from you soon.

    Kind regards

    Ali

    (@alibehvand)

    Hello

    If you’re using Windows 11, go to Accessibility → Visual effects and turn Animation effects ON so transitions work properly.

    However, many people prefer to keep Windows animations disabled for better system performance, while still expecting websites they visit to remain smooth and have transitions.

    In this case, Elementor really needs to come up with a solution for handling this behavior.

    • This reply was modified 6 months, 1 week ago by Ali.
    • This reply was modified 6 months, 1 week ago by Ali.
    Thread Starter Artan

    (@artankrasniqi1988)

    Hi @miloss84,

    sad that I have to report this in GitHub rather then that you deal with it internally now that you have all this information.

    @alibehvand, mate this is not the way to go. Just imagine every developer would force CSS on such a high level (body or html) to all elements. That is just poor CSS and not thought through, like it needed a fast and easy solution without taking into account the possibility of breaking CSS rules of users.

    Also reduced motion means not no motion at all. Also on reduced motion u can have slightly visible animations if you want to have it so. It´s the decision of the developer. But the CSS of Elementor is just killing this.

    Well u can go and put a !important-declaration after all your CSS for transitions. Have fun with that.

    Ah no. Elementor just give me to much headache in the last time. Always throwing stones in my way. I try to get rid of it as soon if I can. These kind of massively bad decisions are not worth the time to run after to fix it. Then I can just better write in plain html and CSS without a builder that causes always conflicts.

    Thread Starter Artan

    (@artankrasniqi1988)

    Hi @miloss84,

    as u said I opened a ticket in GitHub. There u have basically hundreds of unanswered issues that go back months! It seems nobody answers them. So what are u expecting from us users more then to deliver you the problem right there and nothing happens. How is this conflict now solved and who is responsible? Will something happen at all? At the moment I doubt somebody will watch into the issue.

    Plugin Support Milos

    (@miloss84)

    Hi

    Thank you for reaching out and for sharing your concerns. I completely understand your frustration it can be discouraging to open an issue on GitHub and feel like it’s not receiving attention right away.

    I just want to kindly clarify that our developers actively review GitHub issues, but since there are many topics and reports coming in, it may take some time before each one is addressed. We truly appreciate your patience while the team works through them.

    Please rest assured that your issue is not being ignored. It has been forwarded to the relevant team, and once they reach your ticket in the review process, they will investigate it in detail.

    We value the effort you put into reporting the problem, and your feedback genuinely helps us improve. Thank you again for taking the time to communicate this and for your understanding.

    Kind regards,

    Thread Starter Artan

    (@artankrasniqi1988)

    Hi @miloss84,

    Please rest assured that your issue is not being ignored.

    yeah, lets see about that. Seeing hundreds of issues in GitHub reaching back months and still unanswered. Also taking days or weeks for such a massive CSS conflict to fix is just bad.

    Regards

    Plugin Support Milos

    (@miloss84)

    Hi,

    Thank you for your message.

    We truly appreciate your patience while our developers review this and get back to you with an update.

    Kind regards,

    Plugin Support Soyket

    (@soyele)

    Hi,

    I am closing this due to inactivity for a long time. If you are still facing the issue or have new one, please open a new support ticket and our team will look into this for you.

    For change log of updates you can always check this: https://elementor.com/old/pro/changelog/ and https://elementor.com/help/changelog-of-elementor/

    Regards,

    Thread Starter Artan

    (@artankrasniqi1988)

    Hi @soyele,

    the issue is not resolved. So I´m changing the status to “not resolved” back. Thanks, but there is no need for me to open a new ticket with the same issue again. My work here is done and I´m waiting till you get in contact with your developers to remove your CSS code that is causing the conflict. I also opened a ticket in github months ago, as expected nothing happened.

    I´m reopening this ticket until it´s resolved.

    Thanks for your patience.

    Plugin Support Soyket

    (@soyele)

    Hi,

    Development related issues are generally taken care of through github. Since you mentioned you opened a GitHub issue on this, you can expect it to be dealt with there.

    Marking something as resolved or not resolved in this forum doesn’t mean a bug/issue won’t get fixed by developers if reported via proper channel such as github. Since this has been inactive for quite a while now, I will close this. You can follow up on github with our dev team if needed if the issue persists.

    Apologies for the inconvenience & thank you for your co-operation.

    Regards,

Viewing 11 replies - 1 through 11 (of 11 total)

You must be logged in to reply to this topic.