- Shipped
- September 7, 2026 at 11:20 PM UTC
- Author
- Kamo
- Commit
- d707336
Follow-on to the lead-view country-code fix, closing the places that still answered the same question their own way. `NumbersTab` kept a private US-only formatter. Its docblock explained the restraint — "guessing a grouping for an international number produces something that looks authoritative and is wrong" — and that was true of a hand-rolled template, so an org's Moldovan DID sat in the list as the raw run "+37362112345". libphonenumber's metadata is not a guess, so the screen now shares the one formatter and that number reads as "+373 621 12 345". Its test moves with it: a US number reads the way US numbers read everywhere else in the app, and a new case pins the international one the local copy could not group. `telHref` is new, and every "call this" link now goes through it. Display and dialling want opposite things from the same string — one wants spaces and parens, the other wants none of them — and handing the stored number straight to `tel:` works right up until it came from another country and carries a space, which is exactly when the caller can least afford it. It keeps `*` and `#`, which RFC 3966 allows and which are how a feature code is dialled; the open-coded version in ContactDetailPanel stripped them, turning "*97" into extension "97". EventLeadPanel dialled and printed the number exactly as stored — the calendar's "call this lead" chip was the last unformatted number in the app.