Update two manifest member (BCD data removed)

[skyclouds2001]

Description

see mdn/browser-compat-data#23774, the two's BCD data is removed, but the two is still standard: so browser-compat key removed and spec-urls key added, also update Browser compatibility section with a sentence explaining the support status

Motivation

Additional details

Related issues and pull requests

[github-actions]

Preview URLs

• /en-US/docs/Web/Manifest/categories
• /en-US/docs/Web/Manifest/screenshots

(comment last updated: 2024-09-24 02:37:16)

[dipikabh]

Thanks a lot @skyclouds2001 for this PR! You beat me to it :)

The updates are good, just a minor nit with the wording

[Josh-Cena]

This wording implies that they should be supported by browsers but they are not. While if you read the BCD PR the motivation is "this is an app store feature and has nothing to do with browsers". Therefore we should probably say something similar to that: "Browser compatibility is irrelevant because this member is not used by browsers, but by app stores when publishing your app."

[skyclouds2001]

Browser compatibility is irrelevant because this member is not used by browsers, but by app stores when publishing your app.

Agree, but I think the following will be better:

Browser compatibility is irrelevant because this feature is not used by browsers, but by app stores when publishing the app. Though some browsers may use this feature, there is no requirement for browsers to implement any form of support."

[dipikabh]

Thanks for pointing that out @Josh-Cena, that makes sense.

We could word it as:

This manifest member is used by app stores and catalogs when publishing and listing web apps, so browser compatibility is not applicable. Browsers may parse this information, but it's optional and doesn't affect the core functionality of a web app.

@skyclouds2001, WDYT?

[skyclouds2001]

Updated!

[zhowan2020]

[zhowan2020]

Duplicate of #`

[dipikabh]

Thanks!