-
Notifications
You must be signed in to change notification settings - Fork 8
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
Don't show hyperlink for non-number text #5
Comments
Hello! I am new to open source and would like to work on this. Can I take this up? I can contribute more to issues/features/docs etc. once I understand and get this set up. |
Absolutely, let me know if you need any support from my side |
@gitcommitshow Question, for this issue - is it a better idea that the right-click menu shows up only when you select a string that is a number? (Not able to see hyperlink anywhere - if I am understanding this right) |
No. Right click context menu should always be shown. Because this is the default behaviour on browser that people expect. What we want to do now is to add that menu item only if the selected text contained at least 10 digits. |
Got it. So currently in non-number string such as So would you like to change it to just |
We can do one of the following A. Change the text to I would vote for B option, but do whatever you think is the best for good user experience. |
Thank you for the clarification. So based on what I understand, if we go with option B then the menu item won't be displayed if the number is not a valid 10-digit number. Right? And for #9 if we go with tooltip, we can just render WhatsApp icon - this way it can be less annoying instead of rendering text "Whatsapp" on tooltip. |
Yes. And we need to keep in mind - there are different formats for writing numbers that are correct e.g. 99999999, 9999-999-999, +01-9999999999, +019999999999, +920-9999999999 and many more.
Agree. We can put whatsapp icon next to the number so user can see the no. as well as the clickable icon |
No description provided.
The text was updated successfully, but these errors were encountered: