Sorry for the late repsonse. I missed your message
Yeah I think it should be responsively configured else how will you deal with the different screen sizes of iphones, ipads, android phones and android tablets. It would still work otherwise but I’m pretty sure apple will reject the app citing quality of experience or something like that.
Thanks. I checked and there is an issue with your setup. Sent you the DM
I’ve mentioned this to him previously and he’s said that there’s nothing that can be done. I was currently in the process of designing a much better plugin as I’ve seen this is a huge requirement for many people. When I get the time I will resume the development. Here is the forum post:
Hi @gaurav! I’ve got a few ideas for the next release of bdk Phone number input:
Support for an English-only country names (i.e. no local names in the list; there are a lot of usecases for something like that, especially when building tools internal to U.S. companies);
Support for fetching flag emojis from the element (the same way we can now fetch, say, the two-letter ISO code);
Support for moving through input form by pressing the Tab key (currently, when I move through the input form that way and the phone input field comes up next, first two tab strokes are ignored and the third one finally activates it);
Support for the “in focus” conditional (going back to the previous example for a second: when the field gets activated, there’s currently no visual indicator it’s in focus and no direct way to style it using the Conditionals tab).
Anyway, just a few suggestions from a customer. Thank you and keep up the great work!
@gaurav FWIW, the issue @reger-alexander described above should probably have much higher priority than anything from my wishlist. I’ve just encountered the very same bug he had when I placed a Phone Number Input in a group that’s inside of a popup. (In my case, the layout breaks in Safari and Chrome.)
@gaurav One more bug to put on your radar: when the phone input is not set to fixed width in responsive settings, it breaks, the country section disappears entirely, and — for all practical purposes — the whole thing turns into a regular text input, breaking any form validation in place.
Don’t believe this is the case. I’ve changed the demo app editor from fixed width to responsive so you can have a look here. If the input is converting to usual input the way you mentioned, it could happen if the library didn’t get downloaded due to connection issue.