i already have a working workaround, just wanted to confirm that that's a bug, esp. since it only started behaving like that in latest version..