Update non-standard disclaimer

[caugner]

Description

Updates the non-standard disclaimer.

Motivation

See: mdn/yari#9774 (comment)

The non-standard disclaimer makes a valid point, but also the wrong discouragement; designing a website to be exactly the same for all browsers, which may have different default behavior, has never been a valid stance.

Additional details

Related issues and pull requests

Port from mdn/yari#11163.

Fixes mdn/yari#9774.

[hamishwillee]

FWIW This isn't correct and it misses the point of the original issue - which is that you will use this on production sites if you need to. It also will work for everyone if they happen to be on the same browser.

Maybe:

Suggested change

	"en-US": "We do not recommend using this feature on production sites facing the web because it will not work for everyone.",
	"en-US": "This feature is non-standard. Standard features are preferred, but this may be a suitable alternative on some browsers.",

[caugner]

From MDN's authoritative point of view, I think we should explicitly recommend against using non-standard features on production, and explain why. How about:

Suggested change

	"en-US": "We do not recommend using this feature on production sites facing the web because it will not work for everyone.",
	"en-US": "We do not recommend using this non-standard feature in production, as it has limited browser support, and may change or be removed.",

cc @Rumyra

[hamishwillee]

From MDN's authoritative point of view, I think we should explicitly recommend against using non-standard features on production, and explain why.
Agree with @hamishwillee 's suggestion here

I'm not sure which of these came first :-)

@caugner

1. This misses the point that the issue specifically argues that the "you can't use in production" is overly prescriptive.
   That is why I've suggested that these can be used in production, albeit under circumstances where it makes sense.
   You might close the issue as invalid if the MDN position is always "we don't recommend in production full stop".
2. If you do go with something more like yours, then I would make it non-specific to _this non-standard feature" - we apply this everywhere - it isn't really "this" case we're worried about, but the general use.
3. A possible compromise that could meet both needs:

Suggested change

	"en-US": "We do not recommend using this feature on production sites facing the web because it will not work for everyone.",
	"en-US": "We do not generally recommend non-standard features in production, as they have limited browser support, and may change or be removed. They may be a suitable alternative in specific cases, where there is no standard alternative.",

[Rumyra]

Agree with @hamishwillee 's suggestion here