I noticed that in Chromium/Chrome browsers, the clickable area of the text path of a linestring is the entire bounding box of the linestring. Yikes! You can see that on the Leaflet.TextPath demo page (and for more detail, highlight the bounding box using the Chromium/Chrome "Inspect element" feature). Consequently, when one has several clickable linestrings on a page, it's difficult to click the one one wants :-(
This problem does not occur with Firefox, wherein the clickable area is just the text path, thank goodness.
The text was updated successfully, but these errors were encountered:
araichev
changed the title
Chromium/Chrome weirdness
Clickable area of text path is giant in Chromium/Chrome
Dec 9, 2014
Hmm, Leaflet polylines don't suffer the Chrome/Chromium clicking problem. Neither do Leaflet.Label (the plugin) text objects. How about handling Leaflet.TexPath objects in a similar way to those libraries, whatever that way is? If they can do it, you can do it, right?
That's a vague suggestion, but i don't have the expertise to suggest anything more concrete.
Hi there,
I noticed that in Chromium/Chrome browsers, the clickable area of the text path of a linestring is the entire bounding box of the linestring. Yikes! You can see that on the Leaflet.TextPath demo page (and for more detail, highlight the bounding box using the Chromium/Chrome "Inspect element" feature). Consequently, when one has several clickable linestrings on a page, it's difficult to click the one one wants :-(
This problem does not occur with Firefox, wherein the clickable area is just the text path, thank goodness.
The text was updated successfully, but these errors were encountered: