Well, you know why? It's because this issue were reported almost a month back, and since, they have pushed that experimental build, with a few additions and tweaks to stable. They never fixed this issue, and hence, it's now present on stable.

@NinjahMeh Alright, sorry.

NinjaMeh: What are you talking about? My report is 10 days older. 10 days!!! That other person should search first...