News for hackers. Stuff that matters.
Re:Let's Decode a VST by rezonant on Friday June 12, 2020 @11:46PM (#23506592)
Must be an iPhone thing. No problem on Pixel 3XL
Re:Let's Decode a VST by saagarjha on Saturday June 13, 2020 @04:33AM (#23507890)
Yeah, iOS will try to automatically detect phone numbers in web views. It can be annoying sometimes if the web page author doesn’t take that into consideration.
Re:Let's Decode a VST by Log1x on Saturday June 13, 2020 @04:50AM (#23507957)

  <meta name="format-detection" content="telephone=no">
Re:Let's Decode a VST by BuildTheRobots on Saturday June 13, 2020 @08:12AM (#23508857)
And yet in some crazy parallel universe, content authors choose to tag telephone numbers as such to make them clickable, rather than having to tell a browser not to incorrectly interpret text.
Re:Let's Decode a VST by saagarjha on Saturday June 13, 2020 @01:02PM (#23510828)
A crazy parallel universe where iPhone came before the web and could shape it from its inception, surely.
Re:Let's Decode a VST by BuildTheRobots on Saturday June 13, 2020 @08:30PM (#23514080)
RFC-5341 defines "the tel URI for telephone numbers" and is dated December 2004. The first iPhone was released June 2007, so there was already a way of marking phone numbers well before day one.
Re:Let's Decode a VST by tjoff on Saturday June 13, 2020 @08:03AM (#23508824)
Surely apple is to blame for it though.