Skip to main content
Court_Kizer
New Participant
February 28, 2024
Question

Figma Shadow Bugs Introduced Feb 26th. AFFECTED: Dev Mode & CSS Copy

  • February 28, 2024
  • 13 replies
  • 2325 views
  • You can no longer copy css with a right click if box shadow has more than 3 values
  • Box-Shadow Spread Values are discarded.
  • Dev Mode is broken in that it turns box-shadow into css filter: drop-shadow

This was working fine last week, but now it’s impossible to turn it into code correctly. Please investigate.

This topic has been closed for replies.

13 replies

Court_Kizer
New Participant
March 18, 2024

@Tom_Lowry I played with the bug a few hours this weekend. I realized that 90% of this bug is an old regression bug that I reported 2 years ago. It’s mostly because Figma still puts shadows out of order when exporting in both dev mode, and CSS box shadow properties.

This doesn’t happen with other tools analyzing the Figma file. I really want to see this fixed. It means devs can’t reliable use any code generated from Figma with a shadow.

Let me know how I can help. I’m happy to make a video clearly explaining it or anything that would get this up the chain faster.

Tom_Lowry
Figmate
Figmate
March 21, 2024

Hey @Court_Kizer. We had a deploy today that should have fixed the shadow order issue. Can you confirm on your end.

Also lmk if the auto layout frame workaround on your radio/checkbox components solves the box-shadow + css code issue you encountered.

Court_Kizer
New Participant
March 21, 2024

@Tom_Lowry Awesome fix with the ordering. This was directly copy and pasted and it works: Tailwind Play

@Tom_Lowry There is a bug when adding a new Effect. When you click “+”, the animation appears from the bottom, but the new shadow is actually at the top of the stack. Please remove the animation or adjust it to reveal from the top. This is confusing for UI enthusiasts.

Bug:
CleanShot 2024-03-21 at 12.04.10
i