Just to update everyone, our internal testing team could not reproduce this issue yesterday, however we have since received files that show the problem from folks in this thread. Our engineers will investigate, hopefully I'll have something to report later today.
Thanks Neil. I will eagerly wait for any news about it.
@Uwe: Only a small amount of people is reporting a bug/error in a forum or to the support team. Thats my experience telling me from several years as moderator in different forums. Even in a company, where the people work daily together, reporting a bug is not usual. Most people see such bugs/errors as non-working feature that they would not use in future time, don't even thinking that it could be a bug/error.
@Neil – can your engineers pinpoint the issue?
Is there any hint what's causing the bug?
We were able to reproduce the issue using one of the supplied sample files from this thread. It is a new issue in release 22. The reason some people aren't hitting this is it is specific to the authoring in this situation: the object state has a drop shadow applied to it.
The workaround is to remove the drop shadow from the object state. If you really need the drop shadow you can create the object state with the drop shadow in Photoshop, export the state as a static image, and place that in the frame.
Thank you, Neil.
I looked up the applied drop shadow effect in the data Yves sent me by e-mail:
x Offset: 0 px
y Offset: 0 px
Size: 25 px
[x] Object knocks out Shadow
The Size value could be the culprit…
Is it the Drop Shadow effect only?
Or are other effects from the Effects Panel causing this, too?
In my current configuration I cannot test for the bug, because I'm NOT affected…
Any effect that expands the size of the content outside the frame will cause the issue. Outer glow might do it too.