I am wondering how non-http/https URL like dial: should be handled in Constructing a presentation request.

I've found an issue: The recent update on WPT has replaced a URL including Cast ID into dial:. (see web-platform-tests/wpt#7410). This change works well on Chrome, however calling Presentation API on Firefox for Android would result in SecurityError due to the dial: URL

This behavior seems to be based on the current spec:

If any member of presentationUrls is not an a priori authenticated URL, then throw a SecurityError and abort these steps.

I guess that we should additionally consider how to deal with multiple URLs including incompatible one. WDYT?