Tilemap filtering causes visualize exception

[skearns64]

Kibana version: 5.0.0

Elasticsearch version: 5.0.0

Browser version: Chrome

Original install method (e.g. download page, yum, from source, etc.): Elastic Cloud

Description of the problem including expected versus actual behavior: On a tilemap, if I click on the draw a rectangle button, then click on the fit data bounds button, it adds a filter with the same top and bottom bounds.

I originally clicked on the draw a rectangle button by accident, but I assumed that clicking the other button would cancel the draw a rectangle button, because I had initiated a different action.

Steps to reproduce:

[thomasneirynck]

@skearns64 ugh, I can't reproduce this. It seems it was pretty easy for you to repro since you were able to make the video.

What seems to be happening is that you're dragging a rectangle of width=0 between the two buttons, which also would explain why your cursor is changing from a pointer to the crosshairs as your mouse moves between the two buttons.

I'm wondering why the controls think you are dragging a box, when in fact you're just clicking buttons.

Either way, this is a Kibana issue. It shouldn't filter when the bounding box doesn't have a valid width (which causes ES to spit out the error). That needs a fix regardless.

If you can think of any more tips&tricks to try and repro this, let me know.