I think this has been decided that it something we want to live with for 1.0 API and maybe fix in a new API (1.1 or 2.0) ? We may be able to change this back to "Won't Fix"
I think this has been decided that it something we want to live with for 1.0 API and maybe fix in a new API (1.1 or 2.0) ? We may be able to change this back to "Won't Fix"