The position of a text related to an element changes on mouse out

[neveldo]

On mouseout on an element that has a text next to it, the related text moves vertically a few pixel away from its original position.

You can see the bug in the basic/href_areas_plotted_cities.html example when hovering "Rennes" city.

[neveldo]

After some investigation, the issue seems to come from the dy computation of the tspan element (within text element) in Raphael.js (2.1.4) :

L6415 :

        var bb = el._getBBox(),
            dif = a.y - (bb.y + bb.height / 2);
        dif && R.is(dif, "finite") && $(tspans[0], {dy: dif});

The _getBBox() calls the native getBBox() function (L6745). The dy is computed a first time at map initialisation (it happens before calling setViewbox() on the map). Then, it's computed a second time on mouseout (because we call .attr() on the text element to restore the orginal attributes of the text element). The value returned from the second call of getBBox() is slightly different from the first since setViewBox() has been called between the two calls.

See a raw SVG example that shows the issue with the getBBox() function with/without a viewbox defined : https://jsfiddle.net/gfka264b/ , I dont know why the y and height values are slightly different when a viewbox is applied.

Edit : the problem appears on both Chrome and Firefox, v1.1.0 or 2.0.0-dev of mapael.

[neveldo]

A possible solution should be to move the bloc of code responsible of map resizing, ie :

            // Handle map size
            if (self.options.map.width) {
                // NOT responsive: map has a fixed width
                self.paper.setSize(self.options.map.width, self.mapConf.height * (self.options.map.width / self.mapConf.width));
            } else {
                // Responsive: handle resizing of the map
                self.handleMapResizing();
            }

Before drawing the first areas and circles on the map (ie : before "// Draw map areas" comments). I haven't checked the possible side effects of such a move yet, but it seems to work fine at first sight. @Indigo744 I would be glad to have your opinion on it if you have the time to take a look.