Possible bug in Prototype settings for setting the device?

Ask the community
,
1

Hello, I just noticed this possible UI3 bug while setting up a prototype in Figma:

image
image372×106 6.59 KB

I was looking for which device would match the Desktop or Wireframe frame selected in the Design panel, but when I tried scrolling down to view more of the available devices, either there’s nothing after the Macintosh (???) part or this is the end of the list and it’s just not rendering properly.

2

Hey @ChiSenires, Thanks for getting in touch about this and for sharing the screenshot!

I just ran a test on my end, and it seems that the “Macintosh 128K 512 x 342” option is at the very end of the list. I was able to scroll all the way to the end of the list without any issues, both on the desktop app and in Chrome.

Just to clarify, are you experiencing that even when scrolling to the very end of the device list, the last option isn’t fully visible?
If so, to help us better understand the situation and start troubleshooting, could you please check the following for us?

  1. Determine if the issue occurs only on the Desktop app, only on supported web browsers, or on both.
  2. Perform some basic troubleshooting steps to see if there’s any improvement:
    • Browser: Force-quit your current session and try opening Figma in a new browser window.
    • Desktop app: Force-quit the Figma Desktop app and then restart it.
  3. Clear the app or browser cache to check if this resolves the issue.
  4. Try using Figma in an incognito or private browser window to see if there’s any difference.
  5. Attempt to access Figma from a different network, such as using a mobile hotspot, to see if the issue persists.

I hope one of the suggestions proves helpful! Please do let us know if I missed anything or if the issue continues after trying the troubleshooting steps mentioned earlier. If necessary, I’d be more than happy to generate a support ticket on your behalf for additional assistance.

Thanks once again for reaching out!

3

Hi @Junko3, when I did the app cache clearing it solved the issue :smile: Thanks for sharing!

2 Likes