People that want to set a default country (required address field) and hide the widget can simply keep doing things the way we do it now. What we should do instead of adding an extra option in the drop-down widget is to add a -none- country entry to the list of available countries. It breaks use cases where we need to use the 'Hide the country when only one is available' option (there will always be at least two countries/entries: -none- and whichever we choose as the default). I believe that the proposed solution to add a -none- option in the drop-down widget, so it can be set as default for such cases is the wrong approach. That's why in the revised issue title I state that the address field is not *really* optional. *But*, we don't have a way to leave the country field empty no matter what. if no data is entered, there should be nothing saved in the db and no address shown in display. I see the problem here and it is specific to use cases where the address filed needs to be optional: Well, I haven't thought all of these options thoroughly, but you get the point ) ( ) Hide country field from input and content display ( ) Extended - All countries will be allowed. (*) Normal - All allowed countries will be allowed. Require country (Do not allow empty country). Set the site's default language as default for new content.

becomes our new 'Address settings' tab:Д®xtended country options provided by the Address Field module. ( ) Extended, but not displayed - All defined languages will be allowed for input, but not displayed in links. ( ) Extended - All defined languages will be allowed. (*) Normal - All enabled languages will be allowed.

Require language (Do not allow Language Neutral). Set current language as default for new content. So, the equivalent for the 'Multilingual settings' tab:Д®xtended multilingual options provided by Internationalization module. *optionally* hide the address field from content display offer the option to lock this default so it can't be changed (per field instance or content type perhaps) allow admins to set a default country for address fields So, if you really think it through, you'll realize that each physical address has a country (at least it implies one) no matter if we store this information in our db or not. I think that allowing for country will eventually cause similar issues that we are now facing with 'Language neutral' - every text we write is in a certain language no matter if we store this information or not (this very text I'm writing right now is in English - unless we all speak this non-existing language called 'Neutral'). Support from Acquia helps fund testing for Drupal Comments a/devtools/client/webconsole/new-console-output/test/fixtures/stubs/consoleApi.js +++ b/devtools/client/webconsole/new-console-output/test/fixtures/stubs/consoleApi.js -20,175 +20,183 t('ДЄddressfield-nocountry-option-968112-158.patchДЄddressfield-nocountry-option-968112-153.patchДЄddressfield-nocountry-option-968112-149.patchДЄddressfield-nocountry_option-968112-134.patchДЄddressfield-nocountry_option-968112-132_1.0-beta4.patchДЄddressfield-nocountry_option-968112-132.patchДЄddressfield-nocountry_option-968112-124.patchД 001-Issue-3968112-make-addressfield-really-optional.patchДЄddressfield-nocountry_option-968112-98.patchДЄddressfield-nocountry_option-968112-92.patch expect(wrapper.find('.theme-twisty.open').length).toBe(1) // There should be three stacktrace items. a/browser/base/content/urlbarBindings.xml +++ b/browser/base/content/urlbarBindings.xml -179,17 +179,17 file, You can obtain one at } else )) // There should be a collapse button.

Ies ve check for unset components