"+ New Record" button not visible in light mode

Expected:

  • In light mode, the ā€œ+ New Recordā€ button is visible all the time and shows a different style when being hovered over

Actual:

  • In light mode, the ā€œ+ New Recordā€ button is not visible and only is visible when being hovered over

In dark mode, the button is correctly visible all the time:

Sorry @tim.gruenewald,

This seems like a bug. I’ve let the devs know.

A temporary workaround is to set your color palette to ā€œmonochromaticā€ instead of ā€œcustom paletteā€ until this bug is fixed. Sorry about that!

@tim.gruenewald

We got another report of the same issue from another user in your project who was using another environment at the time.

In both of these affected environments, I noticed that some of your colors were set to have an alpha of 1 (nearly invisible / completely transparent, out of a max of 255)… do you know how that might’ve happened? Did someone on your team programmatically set those, perhaps?

I’m also double-checking internally to make sure this wasn’t a bug we might’ve accidentally introduced, perhaps a side effect of dark mode changes.

e.g. your theme object for that environment is set to:

{
	"theme": {
		"logo": null,
		"type": "custom",
		"dark_color": {
			"red": 80,
			"blue": 83,
			"alpha": 255, // standard/max alpha
			"green": 50
		},
		"light_color": {
			"red": 248,
			"blue": 248,
			"alpha": 1, // nearly invisible
			"green": 248
		},
		"accent_color": {
			"red": 234,
			"blue": 94,
			"alpha": 1, // nearly invisible
			"green": 0
		},
		"primary_color": {
			"red": 12,
			"blue": 134,
			"alpha": 255,
			"green": 170
		},
		"hue": null
	}
}

Your colleague let us know this has affected all your environments, and that to their knowledge, nobody did a bulk color update to them. Do you agree with that?

They also tried tweaking the alpha values manually, but some colors still look different from before (like the accent color showing up in places it shouldn’t).

So far we haven’t received other reports from other customers yet. I opened a ticket for investigation, but unfortunately we don’t have a whole lot of info yet, so it’s hard to establish a pattern =/ If we find anything, we’ll report back.

No, nobody did a bulk update to my knowledge

Thank you for confirming. We’ll look into this more.

(EDIT: At customer request, this thread is being continued via email instead. I’ll report back here once the underlying issue is fixed, in case anyone else outside of that org is affected.

But please feel free to post here if anyone else is seeing similar issues with their project.)

This should be fixed now. Sorry about that!