Hi there, how come the background image inserted into a Row is not responsive on mobile device? I thought it would be?
Please see info in private content. Thanks.
This topic has 9 replies, 2 voices, and was last updated 9 years, 6 months ago ago by Eva Kemp
Hi there, how come the background image inserted into a Row is not responsive on mobile device? I thought it would be?
Please see info in private content. Thanks.
Hello,
Try to use this code in Theme Options > Custom CSS > Custom CSS for mobile:
.upb_row_bg {
background-size: contain !important;
}
Concerning the second issue please provide WP admin credentials in Private Content.
Regards,
Eva Kemp.
That Custom CSS doesn’t quite work. When viewed on Mobile Device, it’s showing way too much padding area (Top & Below) the background image.
WP Admin Login is in private content. Thanks.
Hello,
If the image will be set as full width on mobile in will be stretched.
So using “contain” value allows to show responsive image.
I’ve reuploaded the image for Contact page and now it’s shown.
Clear browser cache and check.
Regards,
Eva Kemp.
I changed the Row / Background / Background Image Size to “Contain”, but same results. Still stretched out on mobile. See it for yourself from your mobile device. View the “FAQ” and “Contact” Pages on the site.
Let me know! Thanks!
Also, I haven’t had a chance to update to the latest ROYAL Theme June 4 version yet. Any issues being reported thus far? Royal Theme Updates have changed my Theme Option Settings before, so I just want to make sure first. I do it via FTP.
Hello,
Don’t change image size in Row / Background / Background Image Size. Use this code in Theme Options > Custom CSS > Custom CSS for mobile:
.upb_row_bg {
background-size: contain !important;
}
There are no any problems after theme update.
Don’t forget to create a back up before starting the process.
Regards,
Eva Kemp.
All good now. Thanks for your excellent customer support!
Hello,
You’re welcome.
Regards,
Eva Kemp.
The issue related to '‘ROW Background Image – Not Responsive’' has been successfully resolved, and the topic is now closed for further responses