Bug - Element Transparency not adjustable after setting transparency once.
CC 2018
Placing elements on pasteboard works fine. I adjusted the transparency of the element on layer to 40% over a red box. Now the element shows that transparency. If you try to revise the transparency the properties window shows the element at 100%. There is no way to adjust the transparency back to it's original 100% or know the current transparency.
Anonymous
shared this idea
-
The original problem reported is quite simple, if you open Layers...
Somehow, instead of assigning transparency to the image, the sublayer ('base black') got the opacity applied to. So now all the elements within the sublayer inherit this value. It cascades to all children within the sublayer.
When Layers are opened, the appearance marker (the circular dot) is filled — it means the element (the sublayer) is having a custom appearance. Click the marker to target the sublayer, change the opacity back. Now you would be able to assign opacity to per element, if it was your intention.@Charles — can’t say anything without seeing a file.
@ro ashing -= same deal
@Ken — perhaps it’s a different problem, but please check the Layers in your document, as the attached GIF suggests. Comment back!
-
Ken McElrath commented
I'm using the latest version of Illustrator on a Mac. When I create an item and give it a transparency value, the opacity remains at the value I set until I deselect the item. When I return to item and reselect it, the opacity value says it is 100%. If I try to change the value, it adjusts the transparency of the item to be a factored value. e.g. If I originally set the value to 50%, then later return to the item and change the value from the erroneous 100% to 50% again, the value is changed to 25% (50% of 50%). The only way I can change the transparency value to 100% again is to recreate the item entirely, which is rather ridiculous. This bug is CRITICAL!
-
ro ashing
commented
I cannot make a transparency using Illustrator or photoshop, please help
-
Charles
commented
I am having this problem as well with CC2019
