Comment 2 for bug 1804924

I just discovered that todays nighly does not have this fixed. Has this been marked as fixed on accident, has there been a regression or is there some bug in ubuntus nighly?