Inconsistency: dns.resolve()

[ameshkov]

This inconsistency was discussed during the WECG in-person meeting.

Both Chrome and Firefox support API for using the local DNS resolver.

• https://developer.chrome.com/docs/extensions/reference/api/dns#method-resolve
• https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/dns/resolve

The Firefox version provides more and we would really like to have it supported in Chrome.

How it can be used quickly once it's implemented:

• Functionality for blocking (or discovering) CNAME-trackers
• Service discovery

What needs to be done before that:

• Chrome devs said that the API currently is only available in the dev channel only due to some security concerns. It is important to learn what exactly are these concerns.
• Firefox and Chrome provide slightly different interfaces. Both APIs are already in use. How can this be handled?

[oliverdunk]

Switching from needs-triage to follow-up. On the Chrome side we are going to reach out to our security team to understand if the browser.dns API could be safely exposed.

[Rob--W]

Assigned to Oliver to follow up on the Chrome part; tentatively putting https://github.com/w3c/webextensions/labels/supportive%3A%20firefox on this because the requested capabilities are in Firefox, and if there are differences, we're supportive of seeking alignment.