[w3c/manifest] Don't recommend extensions use vendor prefixing (Issue #1072)

From a discussion on MicrosoftEdge/MSEdgeExplainers#623: it appears that the manifest spec explicitly recommends vendor prefixing in [Proprietary manifest members](https://w3c.github.io/manifest/#proprietary-extensions):

> Although proprietary extensions are undesirable, they can't realistically be avoided. As such, the RECOMMENDED way to add a new proprietary manifest member as an extension is to use a vendor prefix.

Quoting @bathos on that thread:

> Perhaps the [proprietary extensions](https://w3c.github.io/manifest/#proprietary-extensions) section of the Web Manifest spec should be updated to either remove the recommendation that vendor prefixes be used (it surprised me!) or clarify that this advice is (I’m guessing?) meant to apply only to extensions that are truly platform-specific and not intended to be standardized?

I think this is a good idea. Vendor prefixing in the manifest is a bad idea for the same reason it was bad in CSS properties / JS APIs, and we've largely done away with it in favour of things like Origin Trials, which we have happily run on manifest members (like `share_target` and `tabbed` display mode) for years. Let's stop recommending vendor prefixing please.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/manifest/issues/1072

You are receiving this because you are subscribed to this thread.

Message ID: <w3c/manifest/issues/1072@github.com>