Comment by croon

If it's not finished rendering, it should not have a value set to begin with. Why is it populated with the wrong (opposite?) candidate?

Preset values AND slow updates can't be excused like this.