Design Trailblazers

@Bill Hare that black beat on a Cosmos screen-flow picklist is the list panel painting before the option text is ready.

The choices aren't missing, and it isn't a bad picklist value. Cosmos draws the dropdown surface dark, then the options land a moment later. Trying another browser once is still worth it, because an extension can make the paint worse. If a clean Chrome profile and Edge both do it, I wouldn't hold the rollout for a flow change.

I don't have a setup toggle that turns that delay off. What I'd send back on the case is a short recording, Cosmos as the theme, and the screen flow picklist, and ask them to treat it as a Lightning styling defect. The flow itself is fine.

Hi Rajeev,

Since SLDS 2 Dark Mode is currently in Beta, this could be a styling issue with how the In-App Guidance text color is being rendered in Dark Mode. If the text is configured as black but appears pale blue, it may be related to the current theme/token handling. 

I’d recommend testing the same guidance in Light Mode to confirm whether the issue is specific to Dark Mode. If it reproduces consistently in Dark Mode, sharing the browser, Salesforce release, and a screenshot of the In-App Guidance would help with investigation. 

If the issue persists, you may want to create a case with Salesforce so it can be reviewed as a potential Beta UI issue. 

Hi Heath, 

This is a real SLDS 2 rendering behavior, not a config mistake on your end — global actions with longer labels get visually compressed differently under SLDS 2 vs SLDS 1 styling, and there's no admin-facing setting yet to control icon/label sizing in that specific menu. 

Practical options right now: 

1. Revert to SLDS 1 for this sandbox while testing. Setup → Themes and Branding → select an SLDS 1 theme → Activate. This is a fully supported toggle (not a hack), so you can confirm your global actions render as expected under SLDS 1 while you evaluate SLDS 2 elsewhere, without being blocked by this specific issue. 

2. Report it through the official channel rather than working around it silently. Since SLDS 2 is still actively being refined post-GA, this is exactly the kind of feedback Salesforce wants — submit it via the Design System Roadmap feedback link (Trailhead's SLDS 2 support module points to it) so it's tracked against the actual component team, not just a community workaround. 

3. As a partial mitigation if you do stay on SLDS 2: since the truncation is driven by label length, consider whether the action's Label (display name) can be shortened while keeping a more descriptive Description/tooltip — I know you said shortening isn't always possible, but for actions where a shorter label + longer help text would work, that's the only user-facing lever available today without a platform fix. 

There's currently no styling hook exposed to override how global action menu items handle long labels + icons together under SLDS 2 — this is genuinely on Salesforce's side to fix in a future refinement, not something fixable via custom CSS/styling hooks from your org. 

Reference:

Hi , 

Unfortunately, I don't believe Salesforce currently provides a way to selectively enable SLDS 2 for some Visualforce pages while forcing managed-package Visualforce pages to remain on SLDS 1. If a managed package page such as NPSP Contact Merge is broken by SLDS 2, this is likely an issue that must be addressed by the package provider or Salesforce itself.

Salesforce UX Designers should have these two certifications minimum depending on their level and responsibilities: https://trailhead.salesforce.com/en/credentials/designeroverview/

If they are in production delivery they will need additional Consultant and Developer certifications depending on what they are designing for (ie. Admin, Platform App Builder, Business Analyst, Sales Consultant, Agentforce Specialist)