Change Details

Use of the `<source>` tag has been discouraged for years, because of the existence of an HTML element by the same name with an unrelated function. However, "discouraging" the use of a bit of markup, without any formal deprecation, doesn't accomplish anything, to the point that not only are there people who willfully use `<source>` instead of `<syntaxhighlight>`, but there are people who actively object to its replacement with the nondiscouraged tag. A decision should be made to either formally deprecate the `<source>` tag with the aim of removing support in a future MW version, or to stop discouraging its use at all.

Use of the `<source>` tag has been discouraged for years, because of the existence of an HTML element by the same name with an unrelated function. However, "discouraging" the use of a bit of markup, without any formal deprecation, doesn't accomplish anything, to the point that not only are there people who willfully use `<source>` instead of `<syntaxhighlight>`, but there are people who actively object to its replacement with the nondiscouraged tag. A decision should be made to either formally deprecate the `<source>` tag with the aim of removing support in the future, or to stop discouraging its use at all.

Use of the `<source>` tag has been discouraged for years, because of the existence of an HTML element by the same name with an unrelated function. However, "discouraging" the use of a bit of markup, without any formal deprecation, doesn't accomplish anything, to the point that not only are there people who willfully use `<source>` instead of `<syntaxhighlight>`, but there are people who actively object to its replacement with the nondiscouraged tag. A decision should be made to either formally deprecate the `<source>` tag with the aim of removing support in athe future MW versione, or to stop discouraging its use at all.