-
Elfsight widgets injecting
data-eapps-*attributes across entire page and breaking WPBakery layoutsHello,
We are currently using several Elfsight widgets on our WordPress site, including review widgets and popup widgets.
After recent changes, we noticed that the Elfsight platform script is injecting attributes such as:
data-eapps-font-size
data-eapps-line-heightonto a very large number of elements across the entire page DOM, not just inside the widget containers.
For example, the script is modifying elements such as:
-
<div class="vc_row"> -
<div class="wpb_column"> -
<p> -
<a> -
navigation menu items
-
footer elements
These attributes appear on almost every element:
data-eapps-font-size="15"
data-eapps-line-height="28"Our website uses WPBakery Page Builder, and this behavior is causing serious layout conflicts, including:
• unexpected font resizing
• rows and columns collapsing or stretching
• spacing inconsistencies
• responsive layout breakageFrom our debugging we confirmed the behavior originates from the Elfsight platform script:
https://static.elfsight.com/platform/platform.js
Since we use multiple Elfsight widgets (reviews and popups), it appears that each widget initialization is scanning and modifying large portions of the DOM.
Could you please clarify:
-
Why the script is injecting
data-eapps-*attributes across the entire page rather than being scoped to the widget container. -
Whether there is a way to limit DOM manipulation strictly to the widget container.
-
If there is a way to disable the global font measurement behavior that is modifying unrelated page elements.
Ideally, we would like the Elfsight widgets to operate only within their own container and not alter unrelated page layout elements.
Any assistance or recommended configuration would be greatly appreciated.
Thank you.
-
2 Likes
Hi there, @LSOO and welcome to the Community ![]()
I am so sorry about this issue!
As far as I understood, you were using the Elfsight Accessibility widget on your website, which caused issues. I see you’ve replaced it with a different accessibility solution and the issue has gone.
Indeed, there is an issue with the Accessibility widget breaking the inline styles of the website. While our devs are woring on a global solution, we’ve applied a local fix to your widget.
Please add it back to your website and let me know how it’s working now ![]()
1 Like
Hi there!
Great news - a global fix has been released ![]()