You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both variants, with and without prefix, should be supported equally as both have the status de facto and no consensus is in sight.
My proposal is to have a single field backed by both keys:
keys used
proposed behavior
neither specified
empty field that writes the new value to the website key
either specified
updating the value uses the existing key
both specified, different values
shows multiple values watermark
both specified, same value
updates both keys
At the moment, the fields Phone and Website are empty when the keys contact:phone and contact:website are used. Users that are not aware of the Tags section might fill in a new and different value leading to conflicting data.
Both variants, with and without prefix, should be supported equally as both have the status de facto and no consensus is in sight.
My proposal is to have a single field backed by both keys:
website
keyAt the moment, the fields Phone and Website are empty when the keys
contact:phone
andcontact:website
are used. Users that are not aware of the Tags section might fill in a new and different value leading to conflicting data.Some related discussions:
contact:
iD#3915The text was updated successfully, but these errors were encountered: