Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / w3c/contact-picker issues and pull requests
#13 - Provide access to contact's icon
Issue -
State: closed - Opened by rayankans almost 6 years ago
- 4 comments
#12 - Provide access to address properties
Issue -
State: closed - Opened by petele almost 6 years ago
- 8 comments
#12 - Provide access to address properties
Issue -
State: closed - Opened by petele almost 6 years ago
- 8 comments
#11 - Consider Web Intents
Issue -
State: closed - Opened by darobin about 6 years ago
- 7 comments
#10 - Input validation
Issue -
State: closed - Opened by finnurbreki about 6 years ago
- 1 comment
#10 - Input validation
Issue -
State: closed - Opened by finnurbreki about 6 years ago
- 1 comment
#9 - Restrict to top-level navigables
Issue -
State: open - Opened by PaulKinlan about 6 years ago
- 1 comment
#9 - Restrict to top-level navigables
Issue -
State: open - Opened by PaulKinlan about 6 years ago
- 1 comment
#8 - ContactInfo can be a dictionary
Issue -
State: closed - Opened by annevk about 6 years ago
- 2 comments
#8 - ContactInfo can be a dictionary
Issue -
State: closed - Opened by annevk about 6 years ago
- 2 comments
#7 - Consider contact API that does not reveal contact info to the website
Issue -
State: open - Opened by Gozala about 6 years ago
- 11 comments
#7 - Consider contact API that does not reveal contact info to the website
Issue -
State: open - Opened by Gozala about 6 years ago
- 11 comments
#6 - Is there evidence that emerging market users have useful on-device contact databases?
Issue -
State: open - Opened by domenic about 6 years ago
- 6 comments
#6 - Is there evidence that emerging market users have useful on-device contact databases?
Issue -
State: open - Opened by domenic about 6 years ago
- 6 comments
#5 - Consider dictionaries and sequences instead of non-constructible interfaces and frozen arrays
Issue -
State: open - Opened by domenic about 6 years ago
- 3 comments
#5 - Consider dictionaries and sequences instead of non-constructible interfaces and frozen arrays
Issue -
State: open - Opened by domenic about 6 years ago
- 3 comments
#4 - interface ContactInfo: metadata distinguishing email/tel instances?
Issue -
State: open - Opened by inexorabletash about 6 years ago
- 7 comments
#3 - interface ContactInfo: Should name be a sequence?
Issue -
State: closed - Opened by inexorabletash about 6 years ago
- 1 comment
#3 - interface ContactInfo: Should name be a sequence?
Issue -
State: closed - Opened by inexorabletash about 6 years ago
- 1 comment
#2 - interface ContactInfo: Can't use sequence<> as type of attribute
Issue -
State: closed - Opened by inexorabletash about 6 years ago
#2 - interface ContactInfo: Can't use sequence<> as type of attribute
Issue -
State: closed - Opened by inexorabletash about 6 years ago
#1 - API shape: how about navigator.contacts.XXX ?
Issue -
State: closed - Opened by inexorabletash about 6 years ago
- 1 comment