Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clickable area of text path is giant in Chromium/Chrome #22

Open
araichev opened this issue Dec 9, 2014 · 5 comments
Open

Clickable area of text path is giant in Chromium/Chrome #22

araichev opened this issue Dec 9, 2014 · 5 comments
Labels

Comments

@araichev
Copy link

@araichev araichev commented Dec 9, 2014

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.

@araichev araichev changed the title Chromium/Chrome weirdness Clickable area of text path is giant in Chromium/Chrome Dec 9, 2014
@leplatrem
Copy link
Collaborator

@leplatrem leplatrem commented Dec 11, 2014

Thanks for reporting this!

I don't think we can do much about this... Would you have any suggestions?

@araichev
Copy link
Author

@araichev araichev commented Dec 11, 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.

@cbaines
Copy link

@cbaines cbaines commented Mar 21, 2015

Through a long and annoying path, I have figured out one workaround. If you pass "pointer-events": "none" in the attributes, this seems to help.

@araichev
Copy link
Author

@araichev araichev commented Mar 23, 2015

That does the trick. Thanks!

@leplatrem
Copy link
Collaborator

@leplatrem leplatrem commented Apr 1, 2015

Thanks guyz for the feedback !

Anything you could contribute as a pull-request to fix the problem for everybody ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
4 participants