Peter Beverloo

It didn't feel very common for APIs to return (sequences of) dictionaries, but I agree that there's little value in having interfaces. Does https://github.com/beverloo/contact-api/compare/dictionaries make sense to you? The one...

That's much nicer indeed - thanks! Regarding feature detection, a developer would be able to know whether telephone numbers are supported by checking whether `ContactInfo.prototype.tel` exists. That's something we lose...

I have considered this, but I'm not sure where we would draw the line. You could make the same argument about pretty much other data types. Labels can be repeated...

A TypeError will be thrown per [WebIDL semantics](https://heycam.github.io/webidl/#es-enumeration) because `OperationType` is an enumeration.

This is a great question that we have not yet received feedback on beyond the Chrome team. This is a difference that will materially impact the shape of the `getBudget()`...

I think of `background operations`, the currently defined scope of features the spec is applicable for, as a privilege that should never be given to insecure contexts. Removing this restriction...

The `getCost()` method returns the maximum cost of an operation. The actual cost may be lower depending on device conditions (charging, screen state), network conditions and, as you say, details...

We're removing the implementation from Chrome given that it hasn't seen any developer adoption, and interest is very low. While the Budget API provides one possible path towards _silent push_,...

/cc @owencm @johnmellor would love your input on this

The same values should be reused wherever possible. Using the same enumeration is impractical because, while there is some overlap, neither is a superset of the other, which would lead...