Edge 17 already supported [prefer_]related_applications in PWA manifest

[captainbrosset]

Summary

I'm changing the Edge compat data for the related_applications manifest member from false to 17 (and the related prefer_related_applications member).

The reason being that BCD says getInstalledRelatedApps is supported, but related_applications isn't.
This makes no sense since you can't really use the former without the latter. The getInstalledRelatedApps method returns the subset from the apps that are listed in related_applications which are currently installed on the device where the code is running.

So, the apps first need to be listed in the related_applications array, in the manifest, which means that the manifest member is supported.

Test results and supporting details

Finding when this was added is a bit difficult.

The EdgeHTML 17's release notes say that support for PWAs were added to the browser in EdgeHTML 17.
This is confirmed by this Edge blog post from 2018.

The reason I think that support for PWA came with support for related_applications is that the Web App manifest section of the PWA docs from back then does mention the related_applications manifest member.
Using the Wayback Machine, I was able to confirm that the PWA docs did not exist prior to EdgeHTML 17 being released.

[github-actions]

Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs).

[captainbrosset]

@tomayac FYI, BCD says that related_applications is supported only on Chrome for Android, not Chrome desktop. Please let me know if it's actually also supported on desktop.

[tomayac]

@tomayac FYI, BCD says that related_applications is supported only on Chrome for Android, not Chrome desktop. Please let me know if it's actually also supported on desktop.

@captainbrosset I thought it was now with https://issues.chromium.org/issues/40144143 fixed!?

[caugner]

If Chrome did not support this before 139 (chromium/chromium@d05d574), then didn't Edge 79-138 support these either?

[caugner]

Suggested change

	"version_added": "17"
	"version_added": "17",
	"version_removed": "79"

[caugner]

Suggested change

	"version_added": "17"
	"version_added": "17",
	"version_removed": "79"

[captainbrosset]

@tomayac FYI, BCD says that related_applications is supported only on Chrome for Android, not Chrome desktop. Please let me know if it's actually also supported on desktop.

@captainbrosset I thought it was now with https://issues.chromium.org/issues/40144143 fixed!?

This bug is for the getInstalledRelatedApps() method, which is different from the related_apps manifest member.

If Chrome did not support this before 139 (chromium/chromium@d05d574), then didn't Edge 79-138 support these either?

My understanding is that Chrome (and Edge) have had support for related_apps for a long time. This commit is about getInstalledRelatedApps(), which is different. This method does require the existence of the related_apps manifest member, but it was added much later.

So I think this PR, as is, is correct.

[tomayac]

Else, @dmurph is another person who's closer to this.