Remove experimental items from Manifest article

[jpmedley]

The article contained information that is still experimental and is behind a flag in Chrome. I'm working on an update to an article that covers the removed items.

[netlify[bot]]

✅ Deploy Preview for web-dev-staging ready!

Name	Link
🔨 Latest commit	d87b60d107e74c1a165bd81e674885c442c11ef7
🔍 Latest deploy log	https://app.netlify.com/sites/web-dev-staging/deploys/62f42088cb492b0009d4b41f
😎 Deploy Preview	https://deploy-preview-8498--web-dev-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[chrome-devrel-review-bot]

Hello! This is an automated review by our custom reviewbot. It updates automatically when code or GitHub comments in this pull request are created or updated.

Requested changes

If there are any common problems with the content files you created or modified, they will be listed here.

src/site/content/en/progressive-web-apps/add-manifest/index.md

• This file passed all of our automated Markdown audits.

[jpmedley]

They should not be on MDN because they're still behind a flag. (I hope it wasn't me.) I'll check about when these might be shipping by default, but I may need to take them down from MDN as well.

These are in the new article draft I wrote for richer installs.

[beaufortfrancois]

Those items are neither behind a flag, nor experimental anymore. They are supported in stable channel on Chrome for Android and soon™️ on Desktop.

Regarding a new article, we already have https://developer.chrome.com/blog/richer-pwa-installation/. Why is another required?

I wished @jpmedley would have been pinged about this as I was the one authoring this part of the article.

[jpmedley]

It's technically an update because new members are being added to screenshots. Rewriting seemed like the better approach, but I realize that I misunderstood the current state.

[beaufortfrancois]

@jpmedley I'd suggest we add platform to this article and explain it is supported only in Chrome 106 for now.

[jpmedley]

I agree, except that we can't have experimental features on web.dev any more.

Closing this PR because there's nothing I can do to it right now.

[beaufortfrancois]

As @tomayac said, the platform member is not experimental. It is standardised: https://www.w3.org/TR/manifest-app-info/#platform-member

I believe we should document it in web.dev.

[beaufortfrancois]

@jpmedley Do you have plans to update this web.dev article once dcc article is live? If not, I'll do it.

[jpmedley]

I do. Thank you for the offer.

[beaufortfrancois]

@jpmedley What is the current status?

[jpmedley]

I closed this PR because I was misinformed when I opened it.

[beaufortfrancois]

Sorry. I meant about https://github.com/GoogleChrome/web.dev/pull/8498#issuecomment-1229901381

[tropicadri]

@beaufortfrancois I'm taking over the article from @jpmedley I'll sync with you tomorrow