Actions
Bug #1057
closed(Mobile Browser) -- Home page – Scroll down – Latest news section – clicks on Read More button – banner images do not display properly issue:
Start date:
04/22/2025
Due date:
% Done:
0%
Estimated time:
Device/Browser/API:
Mobile Browser
Environment:
Dev
Current Behaviour:
Banner images are not displaying correctly (e.g., not visible)
Expected Behaviour:
Instead, the Banner image should load properly in full view, maintaining its aspect ratio and positioning appropriately for mobile screen sizes.
Root Cause:
Funcational Gap
Root Cause Detail:
Banner images are not displaying correctly (e.g., not visible)
* Instead, the Banner image should load properly in full view, maintaining its aspect ratio and positioning appropriately for mobile screen sizes.
Description
- Banner images are not displaying correctly (e.g., not visible)
- Instead, the Banner image should load properly in full view, maintaining its aspect ratio and positioning appropriately for mobile screen sizes.
Files
Updated by Nikhileshwar Enturi 8 months ago
- Status changed from Open to Clarified
- Assignee changed from Nikhileshwar Enturi to Lakshmi prasanna V
For blog main image is displaying properly and for banner in mobile responsive image appears like that only cannot modify it
Actions
#2
Updated by Lakshmi prasanna V 8 months ago
- File shared image (2).png shared image (2).png added
- File shared image (1).jpg shared image (1).jpg added
- Description updated (diff)
Updated by Lakshmi prasanna V 7 months ago
- Status changed from Clarified to Re-Opened
- Assignee changed from Lakshmi prasanna V to Nikhileshwar Enturi
The banner images display fully on the website, but they are not appearing properly on mobile.
Updated by Nikhileshwar Enturi 7 months ago
- Status changed from Re-Opened to Dev_Inprogress
Updated by Nikhileshwar Enturi 7 months ago
- Status changed from Dev_Inprogress to Resolved
- Assignee changed from Nikhileshwar Enturi to Lakshmi prasanna V
Updated by Lakshmi prasanna V 7 months ago
- Status changed from Resolved to Closed
This issue was verified and closed.
Actions