fix: revert non-standard removal

[dipikabh]

Description

This PR reverts the changes suggested in error via #26817 (review) as pointed out in the BCD PR.
Adding back the header macro and the status front matter key.

[github-actions]

Preview URLs

• /en-US/docs/Web/CSS/-webkit-text-security

[bsmth]

Thanks, Dipika 👍🏻

[andreydanil]

@bsmth Now that FIrefox 14 has been released, should the non-standard label be removed?

[bsmth]

Hi @andreydanil thanks for checking. There's two main ways of marking the status of features, "Experimental" and "non-standard".

• Non-standard means a feature may be supported by multiple browsers in stable versions but isn't defined in a spec.
• Experimental means something is defined in a specification but is not yet widely supported or may change behaviour soon (spec or implementation). This is typically for features that must be enabled through user-set preferences or flags, and this status is usually removed when a feature lands in a stable release (like 114).

I believe this one is still non-standard, but maybe @dipikabh has better context on it.

[dipikabh]

Thanks @bsmth, your answer is on point. Nothing more to add.

The "Specifications" section for this property still says "Not part of any standard" even though the property is implemented in most browsers.

[andreydanil]

Thanks for the follow up 🙂.