Elements 1.2.0 (23816)

is this fixed in the next cms-update?