I don't think my original patch is ever merged.

@Liuxinyu970226 It is not that these codes cannot be converted to JSON. Instead, there's no reason to convert them to JSON. They are statically generated and no one is supposed to change it manually. By keeping them in PHP files, we can actually gain performance from OPcache. If we made them JSON, an extra step of JSON parsing will be required, or extra caching will be needed to compensate the performance degradation.

In T134027#2341426, @demon wrote:

This isn't really 1.27-specific, untagging.

I oppose this change, for users with purge right they should be able to purge without confirmation regardless POST or GET.

In T132538#2316800, @Platonides wrote:

What about repeating them (without port) in $wgSquidServersNoPurge?

This is a bug indeed. The 50,000 url limit is currently imposed on number of articles, instead of number of entries generated.

I am against adding this. As Bawolff said, this could make syntax more complex. We have more straightforward way to solve the problem, for example, like stated in zh.wp's discussion, use a special page that mimics Special:Diff (named Special:Action for example).

@Aklapper "Grants" is the new feature introduced in MediaWiki 1.27 (which is migrated from OAuth plugin), and in DefaultSettings.php, two rights, torunblock and autoreview are listed. I am saying that these two rights are not expected to be there. This is an improper implementation, so reproducing is easy: do a fresh installation and navigate to Special:ListGrants, and you will see these two rights are there.

It can be a great overhead for adding style tags instead of inline styles, if the style is used extensively in a page (this is the case for many fan-wikis, some of them contain a lot of colored texts).

Will adding colors text require use of TemplateStyles then? Some inline style like adding color or change font will not really introduce problems to mobile friendliness and security, why not support both inline styles and TemplateStyles? These could share a codebase for parsing and sanitizing.

In T129499#2152762, @Liuxinyu970226 wrote:

[Citation needed]

Does it really matter? Currently the php file is built by maintenance tool anyway.

Just to comment that position:fixed also affect extensions, such as Flow. I suggest sanitize it completely.