tucker@ Thanks for the issue.

From the original comment, this is a feature request to enable Chrome mdns api for extensions.

Hence marking this as Untriaged for further updates from Dev.

Thanks..

Thanks for fixing the categories susanjun@. Using the issue trackers issue creation wizard I didn't see a way to correctly set the component or type: feature, I was hoping those would be fixed before this got the round bin. 

[Extensions Triage] Assigning to mfoltz@ who is one of the owners of the API to take a look at the request.

Opening up chrome.mdns to third party extensions would require elimination of the service type and extension whitelists, which are important security mitigations for this powerful API.

Instead, I would suggest implementing your application using Chrome Apps which does not have these limitations.

mfoltz@

That would be fine, except chrome apps have been / will be discontinued for our target platform.

https://blog.chromium.org/2016/08/from-chrome-apps-to-web.html

OK, this is a feature request for the extensions/security teams to work though the implications of opening up this API.

Thanks for pushing this along. I'm not perfectly familiar with all of the mDNS specification, I know that it is large and more complex than what our engineers here thought when they implemented it. Even if the whitelisted protocols was small it would be beneficial to us. Our devices are configured over _http._tcp and I think that would/could serve the vast majority of users. 

Hi.  Is there an update on this?  We are experiencing issues with Chromecast list of devices not always populating in Chrome(cast extension) and were looking to make a temp fix by using mDNS API as a Chrome extension to force-flush the list(Without having to restart chrome and WiFi) while we work through this issue with the relevant vendors.