Matt Bierner 5d6cba5cbc Reworking external opener implementation to allow configured openers to be called directly without a canOpen check ...

If the user has configured a specific external uri opener, we should always try to use that without first calling `canOpen` to filter down the list of openers.

This change also adds `ExternalUriOpenerEnablement` which allows an opener to mark itself as the preferred opener for a given uri. If only a single preferred opener is returned, it will be used automatically for that uri (although user configuration can override this)

2021-01-14 10:37:00 -08:00

..

browser

Reworking external opener implementation to allow configured openers to be called directly without a canOpen check

2021-01-14 10:37:00 -08:00

common

Reworking external opener implementation to allow configured openers to be called directly without a canOpen check

2021-01-14 10:37:00 -08:00

node

Merge pull request #114214 from microsoft/tyriar/flow_control

2021-01-14 06:44:30 -08:00

worker

Prefix all performance.mark calls with code/

2021-01-11 16:12:03 +01:00