Open thany opened 5 years ago
Hi! OS version and a phone model, please. Thanks.
Galaxy S9, Android 8.1
Why is this needed? Is this not handled by the app?
No, we use system functions to render html content.
But it isn't html... It's just plain text, isn't it?
No, our descriptions supports HTML, so every description is treated that way.
Okay, so if it's HTML, you shouldn't magically turn things into links. HTML can do that already.
On a sidenote: What masochist types in HTML on their phone? I would much prefer markdown, which requires a lot fewer characters from the secondary keyboard, and can fully serve (what I assume are) the usecases for HTML is a description. But that's a different story.
Okay, fair enough. For your investigation, there are a LOT more kinds of numbers that are incorrectly recognized as phone numbers. So the problem isn't specific to mapcodes. I've seen this happening with prices, where it even has a currency sign before the number.
Mapcodes may look most like a phone number without being one, so perhaps you can take that as the most challenging usecase.
Aaaand..?
Aaaaaaand..?
Aaaaaaaaaaaaaaaaaaand..?
Also I'm on a Galaxy S9 still, but upgraded to Android 10. Issue persists.
Consider this text in a bookmark description:
The app will underline the 592 319 072 part. This is useless, because it's not a phone number, and I verified: tapping it makes my phone try to call that number.
If you don't know, Denso Mapcode is a proprietary "simplified" mapping scheme for Japanese car natsavs.
I would prefer if the app didn't auto-underline phone numbers at all in the description box. Maybe you can add a setting for it.