1284856 - Chart in canvas created via library Chart.js disappears when the cursor moves out of the chart / its canvas.

Status: RESOLVED FIXED

(Core :: Graphics, defect)

Description

[Michal K]

Attachment: Test File

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:50.0) Gecko/20100101 Firefox/50.0
Build ID: 20160706030233

Steps to reproduce:

1. use attached example file - test-bug.html
2. move the cursor over and out of the rendered chart repeatedly - see attached screen recording screen-rec.mov


Actual results:

Rendered chart disappears when the cursor is moved out of the canvas and appears again after moving the cursor over the space of canvas. 
If I use non-e10s window, then the problem occures randomly (not so often), but when I use e10s window, the problem occures every time. It seems that e10s reveals the problem every time.


Expected results:

The rendered chart should not be corrupted / should not disappear if I move the cursor out of the rendered chart. I tested the same file in Safari and the problem is not there. Also I haven't met this problem in official release of Firefox / Chrome.

Comment 1

[Michal K]

Attachment: Screen recording of the problem

Comment 2

[Tooru Fujisawa [:arai]]

possibly a similar issue to bug 1284721.

Comment 3

[Tooru Fujisawa [:arai]]

Regression range: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=57cf7cae92f1b234b763240a33f030fd68fc2166&tochange=56715a33b016d05afc2541e19fd7e0c907258971

Comment 4

[Jim Mathies [:jimm]]

[Tracking Requested - why for this release]:
recent regression from some gfx work

Comment 5

[Marcia Knous [:marcia]]

Tracking 50+ for this recent regression from gfx work. Nicholas can you help here?

Comment 6

[Bas Schouten (:bas.schouten)]

Nical, can you make sure this gets some attention? (Even if it's just some quick additional triage)

Comment 7

[Nicolas Silva [:nical]]

(In reply to Bas Schouten (:bas.schouten) from comment #6)
> Nical, can you make sure this gets some attention? (Even if it's just some
> quick additional triage)

This was fixed a little while ago, I forgot to close the bug.