I almost set this to "Won't Fix" status because it affects AngularJS.
However, I suspect that this interface may not have been ported to Angular, yet.
So, questions:
1. Is this interface available in Angular? 2. If not, is that planned for 3.14-beta? 3. If 3 is true, then will it be likely to get in?
If the answers come out to a majority of true, then I think this bug should be set to "Won't Fix" or the branch adjusted to apply to Angular code.
If not, then it's probably OK to set the target milestone to 3.14-beta.
I almost set this to "Won't Fix" status because it affects AngularJS.
However, I suspect that this interface may not have been ported to Angular, yet.
So, questions:
1. Is this interface available in Angular?
2. If not, is that planned for 3.14-beta?
3. If 3 is true, then will it be likely to get in?
If the answers come out to a majority of true, then I think this bug should be set to "Won't Fix" or the branch adjusted to apply to Angular code.
If not, then it's probably OK to set the target milestone to 3.14-beta.