Skip to main content
New Idea

Some legitimate CSS properties are not recognized by the community platform

Related products:CC Customization
  • February 11, 2026
  • 5 replies
  • 33 views

AndrewK

Hi all,

I noticed several CSS properties are not recognized by the custom CSS interface and result in an error that prevents publishing.

So far, I’ve found the following unrecognized properties:

  • aspect-ratio
  • gap
  • row-gap
  • webkit is also not recognized

 

Idea:

Instead of preventing publishing how about a warning with the option to “Publish Anyway”

 

Thanks!

5 replies

olepord
  • Contributor ⭐️⭐️
  • May 6, 2026

Great idea. I don’t see the downside… 


AndrewK
  • Author
  • Helper ⭐️
  • May 18, 2026

Also overflow-clip-margin


atwhite
Forum|alt.badge.img+1
  • Helper ⭐️⭐️⭐️
  • May 18, 2026

The gap property not being recognized has stymied us more than once. Upvoted!


AndrewK
  • Author
  • Helper ⭐️
  • May 18, 2026

I recently discovered an alternative for that. “grid-gap” is deprecated but recognized and treated as an alias for gap by browsers (works for flexbox and grid) and Gainsight allows this one.


atwhite
Forum|alt.badge.img+1
  • Helper ⭐️⭐️⭐️
  • May 18, 2026

I recently discovered an alternative for that. “grid-gap” is deprecated but recognized and treated as an alias for gap by browsers (works for flexbox and grid) and Gainsight allows this one.

 

Interesting! That’s extremely helpful. Ideally,  full support for current properties would be preferable, but I love a good workaround in the meantime. 😄 Thank you for sharing that!