AddressErrors.languageCode
Deprecated: This feature is no longer recommended. Though some browsers might still support it, it may have already been removed from the relevant web standards, may be in the process of being dropped, or may only be kept for compatibility purposes. Avoid using it, and update existing code if possible; see the compatibility table at the bottom of this page to guide your decision. Be aware that this feature may cease to work at any time.
An object based on AddressErrors includes a languageCode property when the address's languageCode property couldn't be validated. The returned string explains the error and should offer suggestions for how to correct it.
Value
If the value specified in the PaymentAddress object's languageCode property could not be validated, this property contains a DOMString offering a human-readable explanation of the validation error and offers suggestions for correcting it.
This validation might be as simple as ensuring the text of the string is compliant with the syntax defined in RFC 5646: Tags for Identifying Languages (also known as BCP 47), or as detailed as actually verifying that the specified string matches a value from a database.
If the languageCode value was validated successfully, this property is not included in the AddressErrors object.
Specifications
No specification found
No specification data found for api.AddressErrors.languageCode.
Check for problems with this page or contribute a missing spec_url to mdn/browser-compat-data. Also make sure the specification is included in w3c/browser-specs.
Browser compatibility
No compatibility data found for api.AddressErrors.languageCode.
Check for problems with this page or contribute missing data to mdn/browser-compat-data.