[BUG] `InputPhone` removing value leave country code
See original GitHub issue🐞 Bug report
Description
When you hit backspace and remove whole number of InputPhone
, then click away — country code remains in the input, although it is treated as empty value (label flies down). It disappears on the next focus. Can be reproduced on demo portal:
https://taiga-ui.dev/components/input-phone
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
jackocnr/intl-tel-input: A JavaScript plugin for entering ... - GitHub
A JavaScript plugin for entering and validating international telephone numbers ... it will automatically remove the international dial code for you).
Read more >Strange Country Code Problem Causing Messages to Not ...
I am trying to get this corrected without fully deleting the conversation and get the message back to RCS. I can't figure it...
Read more >Working with Phone Numbers in JavaScript - SitePoint
When a carrier runs out of one set of numbers – like, sadly, premium-rate ... Gets the dialing codes for a given country...
Read more >How do I remove the international option in React Phone ...
This will remove international option from the list. ... format for US (213 373 4253) without the "country calling code" part (+1).
Read more >How do I prevent the Country Code from being inclu...
Another troubleshooting step would be to delete the phone number entry and re-add it manually to make sure a country code field isn't...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
WOuld like to know more about this. What would be the ideal case we are looking at here?
Turned out to be an issue with
ActiveZone
emittingfalse
on click while focus was still in the component. Refactored it to wait for nextfocusout
event.