Can you please provide exact reproduction steps for this?

Added NeedsInfo label.

We don't have enough info in this bug to take action. Can you please provide exact reproduction steps?

Added NeedsInfo label.

Having trouble getting this to happen in a small sample for you to test. It only seems to occur in quite a big app I am working on. I will keep trying but have had to go back to the previous editor version for now.

A bit more info:

The Javascript, generated by Dart2js, that causes the error is of the following form:

var t1, t2, screenpoint;
    t1 = this.grid;
    t2 = this.point;
    screenpoint = $.Point$(t1.MathToScreenX$1(t2.get$xposition()), t1.MathToScreenY$1(t2.get$yposition()));

If I manually change the t2.get$xposition() and t2.get$yposition() to t2.xposition and t2.yposition, the error is eliminated.

This issue could be caused by our new type inferrer. One thing we may be able to do is to provide a flag for turning off certain optimizations. However, a reproduction would really be helpful.

Added Area-Dart2JS label.

Added this to the Later milestone.

This comment was originally written by ngeoffray@google.com

Mark, do you have any update for this bug?

Sorry, no. I've tried but I can't seem to reproduce it in a small example project.

For now, I have just added getters and setters for xposition and yposition, even though all they do is retrieve/set private data members _xposition and _yposition.

This seems to work around the problem.

Added TriageForM5 label.

Removed TriageForM5 label.

Removed this from the Later milestone.
Added Oldschool-Milestone-Later label.

Removed Oldschool-Milestone-Later label.