Skip to main content
Inspiring
Nov 14, 2026 2:34 PM UTC
Investigating

P: PS 28.0 - Brush/Masks terrible bugs in Photoshop 2027 v28.0

macOS Golden Gate 27.2.1

Photoshop 2027 v28.0

 

Bug 1: Foreground and Background Colors won’t switch to black/white automatically when a mask is selected.

Steps to reproduce:

  1. Open any image
  2. Click the foreground color and pick any color other than white or black
  3. Create a mask for the layer
  4. The mask is selected, and the foreground/background colors should be automatically set to black/white. But this doesn’t happen.

Workaround: Press D once.

 

Bug 2: You can only paint black on a mask, no matter what the foreground color is.

Steps to reproduce:

  1. Open any image
  2. Create a Curves adjustment layer
  3. Make some adjustments with a curve
  4. ⌘+G to put the Curves adjustment layer in a group
  5. Click on the mask
  6. Press D to set the foreground color to black
  7. Paint on the mask. Sometimes it works, sometimes you are unable to paint at all.
  8. If it works, press X to switch the foreground color to white, then paint on the mask.
  9. You are still painting black

Simpler way to reproduce:

  1. Open any image
  2. Create a mask for the layer
  3. ⌘+G to put the Curves adjustment layer in a group
  4. You can only paint black

You can also try with an inverted mask.

Workaround: Hold alt and click on the mask to disable it, then re-enable it.

 

Important Notes:

  • I believe these 2 bugs are related. When editing masks, my foreground/background colors will suddenly change to random grayscale colors. But I have yet to find a way to reproduce it.
  • Bug 2 only happens when you put the adjustment layer in a group (just like the HSL bug).
    Pinned Reply By James318060693eri

    ive had some success with switching off the new Modern Color Interface (preferences - >  Interface).  I dont really think this is very well implemented so far, and switching it off does tend to improve the issue

    24 replies

    robertw44482386
    Inspiring
    Nov 18, 2026 2:51 PM UTC

    What sucks is that the engineers make them selves available to help us solve these egregious issues and they take the blame for it. But I guarantee this is a management issue. There is no way the people who actually wrote the code didn’t know it was flawed in beta and knew it would be flawed in release. I’m sure they didn’t want to release it but a manager or executive forced it. Those managers are nowhere to be found here. No one has even bothered to answer the question of why. I’m grateful for the engineers answering the “how” but it is time for the suits to stand up and answer “why did this happen?”

    Translate
    ModernAlchemy
    Participant
    Nov 18, 2026 1:55 AM UTC

    What exactly is Adobe testing before shipping these updates? What possible standard of quality control allows something this catastrophically basic to make it into a production release? How does a company with Adobe's resources, revenue and decades of experience manage to break the very functionality upon which its software was built?

    A month on, and we're still paying a premium for half-baked software that cannot reliably perform a function Photoshop first shipped over 30 years ago.

    The fact that Adobe's paying customers are effectively being conscripted as unpaid quality-assurance testers is an indictment of the company's priorities.

    This is a spectacular failure of product stewardship, and an embarrassment for a company that once set the standard for professional creative software.

    Translate
    xxCounterpoinTxx
    Inspiring
    Nov 15, 2026 9:13 AM UTC

    These are problems that were in the beta!!!! 

    They released it anyway!!!!

    They are STILL not fixed in the 28.1 beta!!!!!!!

    They knew about this problem and released it anyway. Shame!!!!!!!!
     

     

    Translate
    Sameer K
    Community Manager
    Community Manager
    Nov 16, 2026 12:21 PM UTC

    Hey, all. I've notified the team about this who are already working on it, since it was flagged in Photoshop (beta).


    Thanks!
    Sameer K
    (Type '@' and type my name to mention me when you reply)

    Translate
    BP1510
    Known Participant
    Nov 14, 2026 1:07 AM UTC

    This is also happening in PS V.28 how is this not checked before the program is released to users??

    Translate
    BP1510
    Known Participant
    Nov 14, 2026 1:04 AM UTC

    I just download PS V28, and this was the first thing that I found out. Painting (Dodging and Buring) on masks is one of the most basic and fundimental processes Photoshop can offer photographers. It is a technique that is founded from darkroom printing from film days. How on earth can this not be checked before the main update is released.

    This is the pupose of having a Beta program, so bugs like this are picked up before they are released… but even further to that, checks should be made before the version is released to users.

     

    Translate
    Participating Frequently
    Nov 13, 2026 3:14 PM UTC

    Closing in on a month of this. Still having this issue of switching to the mask layer and not having pure black / white be the default. Instead, the existing swatches are being inherited and converted to their grayscale equivalents.

    I recently thought I was painting with pure black, but it turned out that it was dark gray (due to this bug). I only caught this because I had the mask layer as the only visible layer and noticed that it was still faintly visible after being brushed.

     

    Translate
    Participant
    Nov 13, 2026 10:32 AM UTC

    I am having the same frustrating problem - brush stuck in same color. And nope, no workarounds or step-by-step solutions are working.

    Translate
    Viva-LaVigne
    Participant
    Nov 12, 2026 2:53 PM UTC

    I feel like they’re vibe coding photoshop now. I downloaded the Art Craft suite. Wow.

    Translate
    Viva-LaVigne
    Participant
    Nov 12, 2026 2:52 PM UTC

    It thinks the app has been updated 4 times, and this problem is getting worse.

    Translate
    Known Participant
    Nov 11, 2026 8:36 PM UTC

    ive had some success with switching off the new Modern Color Interface (preferences - >  Interface).  I dont really think this is very well implemented so far, and switching it off does tend to improve the issue

    Translate