Backround overlay gradient position values not loaded for tablet and mobile if set to "custom" value. #27286
Labels
status/awaiting_triage
Indicates when an Issue, Pull Request, or Discussion awaits to be triaged.
Prerequisites
Description
I want to use "custom" values for a section background overlay gradient position value with different values for desktop, tablet and mobile. The Problem is on tablet and mobile screens the desktop value is loaded no matter what i type in tablet or mobile. I also tried to use just the background with custom gradient position values but this also did not work.
Steps to reproduce
CSS rendered in Frontend for all devices:
background-image: linear-gradient(180deg, var(--e-global-color-143b424) 120px, #FFFFFF00 120px);
Expected behavior
CSS rendered in Frontend for desktop:
background-image: linear-gradient(180deg, var(--e-global-color-143b424) 120px, #FFFFFF00 120px);
CSS rendered in Frontend for tablet:
background-image: linear-gradient(180deg, var(--e-global-color-143b424) 100px, #FFFFFF00 100px);
CSS rendered in Frontend for mobile:
background-image: linear-gradient(180deg, var(--e-global-color-143b424) 80px, #FFFFFF00 80px);
Isolating the problem
Elementor System Info
== Server Environment == Operating System: Linux Software: Apache MySQL version: mariadb.org binary distribution v10.11.4-MariaDB-1:10.11.4+maria~deb11-log PHP Version: 8.2.18 PHP Memory Limit: 1024M PHP Max Input Vars: 4000 PHP Max Post Size: 256M GD Installed: Yes ZIP Installed: Yes Write Permissions: All right Elementor Library: Connected == WordPress Environment == Version: 6.5.3 WP Multisite: No Max Upload Size: 256 MB Memory limit: 256M Max Memory limit: 1024M Language: de_DE Timezone: Europe/Berlin JS: showing 2 of 2JS: 2024-05-06 03:59:59 [error X 2][.../wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.21.4:2:30429] elementor.settings.page is undefined JS: 2024-05-09 15:02:41 [error X 1][.../wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.21.5:3:54579] $ is undefined
Agreement
The text was updated successfully, but these errors were encountered: