Open the linked story
shkspr.mobi
1–10 of 74 posts
Re: <input type=“country” />
#2I have my doubts as to whether a generic solution solves this.
The author notes some issues, like using it for place of birth. Now you need a temporal list for "countries that existed in year XYZ".
There are similar issues for shipping. Not everyone ships everywhere. If the list is abstract and unknown to me, how do I whitelist/blacklist? Am I supposed to know that Scotland exists in the list or not? What if it's for a passport input? Does Scotland have it's own passport? How do I deal with Taiwan without pissing off Chinese web site visitors?
Tldr: The list depends on context. I'm skeptical that a centralized list could deal with commonly used contexts.
Re: <input type=“country” />
#3now tie that to a SaaS that helps you manage those countries
Re: <input type=“country” />
#4I'm mostly just impressed that HN allows brackets in the title...
Re: <input type=“country” />
#5How do you define a country? Is it what current western world considers a country? Meaning whatever US and EU allies (puppets) + Japan decide?
Definition of a country is very flexible thing and depends on current political order. I.e. is Tibet a country?
Re: <input type=“country” />
#6Just do longitude and latitude. Show a map of the earth and let them drop a pin.
There is no reasonable way to get the world to agree on a single list. I doubt you could get browser developers to agree on a single list. For example Apple listing Taiwan in Safari could get Apple kicked out of mainland China. There is simply too much politics here to be tenable.
Re: <input type=“country” />
#7Just do longitude and latitude. Show a map of the earth and let them drop a pin. There is no reasonable way to get the world to agree on a single list. I doubt you could get browser developers to agree on a single list. For example Apple listing Taiwan in Safari could get Apple kicked out of mainland China. There is simply too much politics here to be tenable.
How do you propose visually impaired users use that interface?
Re: <input type=“country” />
#8Classic simple problem that's impossible to solve.
The thought that web browsers support could solve this problem speaks volumes about the kind of rate people _think_ software gets updated. You could never trust input=country to be supported much less up to date thus it will always be poly filled by some library. So why the false hope?
Re: <input type=“country” />
#9How do you define a country? Is it what current western world considers a country? Meaning whatever US and EU allies (puppets) + Japan decide? Definition of a country is very flexible thing and depends on current political order. I.e. is Tibet a country?
And what do you do when China shows up and says "We're blocking your download servers unless you take Taiwan out of the `country` input"?
Better to not centralize the failure points that political actors can put pressure on for what gets to be a country or not.
Re: <input type=“country” />
#10Just do longitude and latitude. Show a map of the earth and let them drop a pin. There is no reasonable way to get the world to agree on a single list. I doubt you could get browser developers to agree on a single list. For example Apple listing Taiwan in Safari could get Apple kicked out of mainland China. There is simply too much politics here to be tenable.
I know what we should do! A dropdown with every possible latitude and longitude combination.