Double clicking a spot swatch in the Swatches Palette allows you to rename the swatch. In past versions, Illustrator would not allow you to rename the spot swatch if it was used in a linked or embedded image. Now the spot swatch can be renamed whether or not it is used in an image. There is no warning that the spot being renamed is in use. After renaming the spot swatch, the Swatches Palette does not show the spot actually used in the image. Changing the color values of the spot swatch before renaming changes the appearance of the image, but it does not after renaming. After saving and reopening the file, both the original spot(used in the image) and the renamed spot swatch will be visible in the Swatches Palette.

I've observed this behavior in the following installs:
MacOS 11.5.2, Illustrator versions 25.3.1 & 25.4.1
Windows 10, Illustrator version 25.2.1

It is important that the Swatches Palette correctly reports the spot colors used in images. The renaming of a spot swatch used in an image breaks at least one of the save scripts we use in production. It also causes an error upon saving on machines with Esko plug-ins installed.

Dell xps 13, i7, 16gb, Windows 10.
Illustrator 25.2

Attempting to use a Free-form Gradient (FG) as a Fill and a simple shape as a mask, using the Opacity Mask tool. As soon as I click away from the Opacity sub-menu, the FG disappears. Even the swatch icon has no black outline.

It is easily solved by expanding / flattening transparency, but I need a non-destructive method. The file uses global colours, as i need to change a lot of icons at once at a moments notice, but that feature gets lost once the shape is expanded / flattened. I've tried a simple clipping mask with the same results.

Below are examples of expected results using an expanded shape vs live free-form gradient tool

In Photoshop, when we open the Color Picker window and are dragging the cursor over the color brightness area (the square which shows the different shades of the current color of the color wheel) and then while dragging, if we move out the cursor from any of the edges or corners of that square area, the color on the edge gets selected. That's the ideal behaviour.

In Illustrator, when we drag out the cursor from a corner (For example, to select black color, I'd quickly drag out the cursor from the bottom left corner) Illustrator resets the color to the previously selected color instead of the color in the corner (in my case, black color).

Please change this behaviour, and make it similar to how it is in Photoshop.
Thank you!

The Deuteranope confusion point was published as xy = (1.08, -0.08) in color vision texts circa 1970.

However, the currently accepted Deuteranope confusion point is xy = (1.40, -0.40).

Unfortunately, Adobe Illustrator appears to use the OLD confusion point in the Color blindness - Deuteranopia-type proof mode. As a result, the simulation is inaccurate and inconsistent with current vision science understanding.

This may affect other Adobe products as well but I have not checked those. A comprehensive check should be performed to ensure the Deuteranopic confusion point is updated to the modern standard, xy = (1.40, -0.40) everywhere.

The attached document demonstrates the problem.

Hi all.
Since I was asked by one of the Adobe employees, here's my post.
Windows 10.

I am getting seriously miffed. After using Illustrator ever since the nineties I can no longer do what I need so, so often: duplicating a color stop in a gradient while keeping the other stops as they are.

Say I have the following:

Stop 1 - position 0 - Opacity 0
Stop 2 - position 25 - Opacity 100
Stop 3 - position 75 - Opacity 100
Stop 5 - position 100 - Opacity 0

I need a zero opacity stop on position 50 and 'Alt-drag' the stop on either 0 or 100 to position 50 to copy it.
This always worked, but no more.
Instead, in the latest version it removes the opacity values from every stop it passes.

If I 'Alt-drag' an opaque stop the same happens, all stops that used to be transparent are now fully opaque.
It sometimes even affects stops in the vicinity, sigh.

I can't work like this. I mean, I know workarounds, but I simply want to get on and work normally (fast). Can we hope for a speedy fix?