Apex Code Development You need to sign in to do that
Don't have an account?
Jugbeer Bhola FORM_FACTOR not recognized as changing in Chrome Dev Tools
Developing a Lightning Web Component.
When initially working on the PC, the Chrome browser displays my form with a FORM_FACTOR of LARGE.
I would like to test the screen in a mobile size SMALL also. I opened the Chrome developer tools. I toggled the device mode to an iPhoneXR.
While in the device toggle to iPhoneXR the image is scaled down to phone size.
The problem is that the browser still thinks the FORM_FACTOR is LARGE.
The size of the screen changes but the lightning component does not acknowledge that the viewable area has changed its display size.
Is there a workaround to this?
When initially working on the PC, the Chrome browser displays my form with a FORM_FACTOR of LARGE.
I would like to test the screen in a mobile size SMALL also. I opened the Chrome developer tools. I toggled the device mode to an iPhoneXR.
While in the device toggle to iPhoneXR the image is scaled down to phone size.
The problem is that the browser still thinks the FORM_FACTOR is LARGE.
The size of the screen changes but the lightning component does not acknowledge that the viewable area has changed its display size.
Is there a workaround to this?
Seems like this is browser specific issue. Check steps mentioned below or would recommend you to log a case with salesforce support.
https://help.salesforce.com/s/articleView?id=000312846&type=1
Hope above information was helpful.
Please mark as Best Answer so that it can help others in the future.
Thanks,
Anybody help?
Raymond, Initially, when you enter the browser, FORM FACTOR is LARGE. When you toggle to an phone there is not a page refresh so the FORM FACTOR still sees LARGE until you refresh the page.
Hoping for a better answer but the toggle would have to do a page refresh. That does not happen.
To avoid a lot of back and forth the testers were required to use an actual phone instead of the browser toggle. They did not like it but otherwise they were likely to log unneccessary issues.