I thought I would throw this out there - anyone see an issue with cosmos where you click a picklist/dropdown in a screen flow and there is a second or two where the choices go black and then show the list?
We tried opening a case with SF and after a couple of weeks - nothing really came of it - was told to try different browsers and or networks - want to turn it on for our users but not sure we like that behavior - thanks!
Hi @Fiona Tang,
I am aware that Dark Mode is currently in Beta, but wanted to share a UI issue with In-App Guidance. Text that has a Black Font Color is looking pale blue, making the text hard to read. Could you please take a look into this?
Here is an example:
Thanks,
Raj
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.
I am testing out the new SLDS V2 styling in one of my sandboxes and I noticed that when clicking on global actions, the icons that I added are now being compressed due to the length of the names (in SLDS it just doesn't show the whole name). Other than shorting the name of the global action, (which is not always going to be possible). Thoughts? Options?
#Design Strategy #SLDS Styles #Nonprofit
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:
https://trailhead.salesforce.com/content/learn/modules/salesforce-lightning-design-system-2-for-developers/get-help-and-support-with-slds-2We'd like to turn on the setting to use SLDS 2 for pages that include <apex:slds> when an SLDS 2 theme is active in User Interface in order to take advantage of dark mode and SLDS 2 for our custom Visualforce pages.
However, when we do so, some of our managed package Visualforce pages have significantly degraded appearance. This includes Salesforce's Nonprofit Success Pack Contact Merge page in particular.
Is there a way to enable SLDS 2 on particular Visualforce pages (the ones we have control over) and leave SLDS 1 for the managed package ones that we can't update (and may not be able to get Salesforce to update)? It looks like there is a way to force <apex:slds> to use SLDS 1, but that doesn't really help us as we can't edit the managed packaged pages where that would be necessary.
I can try opening a Salesforce support case, but since they started replacing everything with AI, it's been much more difficult to get a decent response. I suspect the answer will be to create an Idea, which will then languish for years or just be closed (which doesn't really help solve our problem).
@Nonprofit Success Pack @Design Trailblazers
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.
It appears that in the Winter '27 release the "Header and Three Regions" App Page template is no longer configured with three equally sized regions, defaulting to a 60-20-20 split. I can't find anything in the release notes about this. Is this a planned change or an error in the release preview?
After enabling an SLDS2 Theme we are having reports from users that some text is difficult to read on certain monitors. In particular it seems to be the default text in list views, where the color is a light gray. I have tried changing the accent colors in the 'Advanced Configuration' section but this seems to make no difference. I have tried the default 'Salesforce Cosmos' theme as well as a new theme with the brand color set to #000000 (black) but nothing seems to change the color of this particular style of text.
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)
We have noticed that some text in emails and comments section of cases are hard to read when the text there is black or gray. Users have to switch to light mode to read that.
Hi @Jeremy York, I'm the PM for Dark Mode & SLDS 2. You are correct Dark Mode is currently in beta, so thank you for reporting this bug. I was able to reproduce this issue in a test org on the chatter feed, so I will get this triaged in our backlog to fix. Let me know if you have encountered any other Dark Mode issues!