We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hello 🙂.
It's not a big problem, but it is a bit annoying. 😅.
When a page is loaded, the CSS of the "lang switcher" seem to load 1sec after the rest of the page.
Every time a page is loaded, the problem occurs. The result is a small lag in the page, especially when the widget is integrated into the header.
The HTML is displayed correctly, but for 1 or 2 seconds, the CSS does not cover the cpel_switcher.
Just a guess, but I've noticed that the plugin's CSS resources load in the footer, not into the header.
I've disabled the cache, or other plugins, but the problem is still there.
By the way, this plugin is really useful 😀
The text was updated successfully, but these errors were encountered:
Edit : I found the solution on the previous issues.
#3
The solution was very simple: load the CSS in the header instead of the footer.
add_action( 'elementor/frontend/after_enqueue_styles', function(){ wp_enqueue_style( 'cpel-language-switcher' ); } );
Sorry, something went wrong.
No branches or pull requests
Hello 🙂.
It's not a big problem, but it is a bit annoying. 😅.
When a page is loaded, the CSS of the "lang switcher" seem to load 1sec after the rest of the page.
Every time a page is loaded, the problem occurs. The result is a small lag in the page, especially when the widget is integrated into the header.
The HTML is displayed correctly, but for 1 or 2 seconds, the CSS does not cover the cpel_switcher.
Just a guess, but I've noticed that the plugin's CSS resources load in the footer, not into the header.
I've disabled the cache, or other plugins, but the problem is still there.
By the way, this plugin is really useful 😀
The text was updated successfully, but these errors were encountered: