The "Corrected Version" there, I just turned off this CSS in dev tools:
left: 0;
margin-left: -140px;
Those dec's are inline, and seem to be injected by theme or wpb related javascript.. so we can't really wrench control over that.
DETAILS:
We've done an incredible amount of testing to try and fix this ourselves. It seems this is specifically related to using the most recent version of Salient's Child Theme.
E.g. activate parent theme and the problem goes away. Activate child, it comes back. We meticulously tested this removing everything from the child theme folder, literally.
CHILD Functions.php:
We even tried commenting out lines in the Child Functions.php, and to the best of my recollection, the line
Curious if you guys know what causes that issue though. Also adding that CSS dec does seem to fix it, but not without maybe affecting a few existing CSS rules negatively.
PROBLEM:
Full Width Content Rows render partially off page on mobile.
Image of Broken Version
Image of Corrected Version
The "Corrected Version" there, I just turned off this CSS in dev tools:
Those dec's are inline, and seem to be injected by theme or wpb related javascript.. so we can't really wrench control over that.
DETAILS:
We've done an incredible amount of testing to try and fix this ourselves. It seems this is specifically related to using the most recent version of Salient's Child Theme.
E.g. activate parent theme and the problem goes away. Activate child, it comes back. We meticulously tested this removing everything from the child theme folder, literally.
CHILD Functions.php:
We even tried commenting out lines in the Child Functions.php, and to the best of my recollection, the line
wp_enqueue_style( 'parent-style', get_template_directory_uri() . '/style.css', array('font-awesome'), $nectar_theme_version);
is required, but also reintroduces the problem.
Please help!!
PS, I did find one person with basically exactly the same problem: https://themenectar.ticksy.com//ticket/1744951/
Curious if you guys know what causes that issue though. Also adding that CSS dec does seem to fix it, but not without maybe affecting a few existing CSS rules negatively.