The subtitle is just annoying and disruptive, IMHO. It doesn't seem worth it... I'm reverting in r42664 and marking this bug WONTFIX. If somebody comes up with some good UI models we might reconsider it.

herd wrote:

*** Bug 16649 has been marked as a duplicate of this bug. ***

Given the introduction of [[mw:Help:Page status indicators]], I believe this can now be implemented, deprecating scripts such as these

• https://pt.wikipedia.org/wiki/MediaWiki:Gadget-Topicon.js
• https://fr.wikipedia.org/wiki/Utilisateur:Gz260_test/monobook.js

(In reply to Helder from comment #28)

Given the introduction of [[mw:Help:Page status indicators]], I believe this
can now be implemented, deprecating scripts such as these

• https://pt.wikipedia.org/wiki/MediaWiki:Gadget-Topicon.js
• https://fr.wikipedia.org/wiki/Utilisateur:Gz260_test/monobook.js

Yes, but the concept is that these will be done per-wiki (or perhaps per farm), and not in MediaWiki itself. Consequently should this be tracked here?

Is the way forward then to create a separate extension that does this and enable it on Wikimedia wikis?

In T12347#1193895, @Lydia_Pintscher wrote:

Is the way forward then to create a separate extension that does this and enable it on Wikimedia wikis?

I suppose this is what this task is about. Then JavaScript would not apply.

Is there a way we could implement this by default, and still allow the wiki to override ?
I actually find it a bit of a shame that we don't use indicators unless implemented by a wiki. I mean if you download the software, I expect that to just work, without any interference from a template author..

We could add a switch to render some by default, enabled by default in core and disable on wmf properties perhaps ?

We could. If we use the indicator system from T25796 for this, and use an indicator name that is also valid in <indicator> (I don't think we disallow any :P), and add our indicator with OutputPage::setIndicators() before the ParserOutput is added – then the indicator could naturally be overridden/hidden from wikitext.

see T20418

wp-en has working Lua code in https://en.wikipedia.org/wiki/Template:Documentation

@TheDJ or @matmarex do you know the current state of this one? Will see what I can do if still open since we're about to look at indicators in the desktop improvements project.

It seems free for taking to me. I suggested earlier using the indicator system:

In T12347#1910365, @matmarex wrote:

We could. If we use the indicator system from T25796 for this, and use an indicator name that is also valid in <indicator> (I don't think we disallow any :P), and add our indicator with OutputPage::setIndicators() before the ParserOutput is added – then the indicator could naturally be overridden/hidden from wikitext.

In T12347#6779891, @matmarex wrote:

It seems free for taking to me. I suggested earlier using the indicator system:

In T12347#1910365, @matmarex wrote:

We could. If we use the indicator system from T25796 for this, and use an indicator name that is also valid in <indicator> (I don't think we disallow any :P), and add our indicator with OutputPage::setIndicators() before the ParserOutput is added – then the indicator could naturally be overridden/hidden from wikitext.

Given we show a locked icon next to edit on mobile that would perhaps be a little confusing when we finally render indicators on mobile.
Paging @alexhollender - how do we plan to visually tell somebody a page is protected on desktop?

In T12347#6793736, @Jdlrobson wrote:

Given we show a locked icon next to edit on mobile that would perhaps be a little confusing when we finally render indicators on mobile.
Paging @alexhollender - how do we plan to visually tell somebody a page is protected on desktop?

As far as I know we're not planning any changes regarding page indicators aside from moving them slightly. People currently can see that a page is protected from the icons editors place on the page. cc @ovasileva

just remembering that we did have an aspirational idea early on that we would communicate whether or not a page is locked/protected within the Edit button (similar to what we do in Minerva)

I feel like communicating that within the edit button makes more sense than adding an additional indicator for it

In T12347#6797373, @alexhollender wrote:

just remembering that we did have an aspirational idea early on that we would communicate whether or not a page is locked/protected within the Edit button (similar to what we do in Minerva)

I feel like communicating that within the edit button makes more sense than adding an additional indicator for it

That unfortunately wouldn't work for the entity pages on Wikidata since they don't have a global edit button but instead a lot of edit links for each statement, etc.

Can someone please clarify what the purpose/proposal of this task is? Otherwise I think we should close it given it was filed in 2007 and there has been little discussion on it since then.

• The title of this task is Add page indicator to show that the page being viewed is protected. As far as I am aware we already do this, and have no planned changes.

• Some comments mention adding text / additional elements to indicate the page is protected. Why is this necessary? I agree with T12347#150059

In T12347#6953316, @alexhollender wrote:

Can someone please clarify what the purpose/proposal of this task is? Otherwise I think we should close it given it was filed in 2007 and there has been little discussion on it since then.

• The title of this task is Add page indicator to show that the page being viewed is protected. As far as I am aware we already do this, and have no planned changes.

MediaWiki core has not and does not indicate protection status visibly besides the subtle lack of an edit button, or "view source" rather than "edit". Subsequently, many/most wikis have templates and modules providing that classic lock icon for what is seen to be as a deficiency.

I suspect the reason it has not been commented on is because fixing it is taken to be a given. I'm sure I can go onwiki and ask users to leave feedback, but I expect that would be a bunch of +1s rather than meaningful feedback. Your conclusion that it means something that the task hasn't seen a comment and thus it should be closed is unsupported.

It is not reader-friendly to be lacking the less-subtle cue, or i18n friendly for every wiki to implement this on its own, or external MediaWiki users to require the same as each editor, and can lead to "non-standard" appearance and editor/MediaWiki user annoyance that to provide this icon they may need to do it themselves or via a bot, changing the page content to emit a lock. (Which is dumb.) Which you seem to understand is what happens. The point of the task is ultimately to make it appear automatically as a result of the protection itself rather than require editor or bot workaround.

@Izno thanks for the clarification. If I am understanding your comment correctly it seems like the main issue here is the technical method with which indicators/notices appear on pages, rather than the visual presentation of those indicators/notices. Is that correct? If so, would you be willing to update the task title and description to clarify that this is about making a technical change, rather than a visual change? It might also be appropriate to open a related task regarding the visual appearance (ie I think it would be better to discuss in a separate task).

In T12347#6953587, @alexhollender wrote:

@Izno thanks for the clarification. If I am understanding your comment correctly it seems like the main issue here is the technical method with which indicators/notices appear on pages, rather than the visual presentation of those indicators/notices. Is that correct? If so, would you be willing to update the task title and description to clarify that this is about making a technical change, rather than a visual change? It might also be appropriate to open a related task regarding the visual appearance (ie I think it would be better to discuss in a separate task).

Well, as you can pointed out, the change was previously reverted for aesthetic reasons, so I don't think this task will close before the aesthetics are sorted. If you want the related task to block, I can reorganize stuff, but that seems like just enough effort to decline on my part until then. :^)

I boldly added a couple downsides for the manual approach; please remove if that was inappropriate, since I don't know if there's some extra etiquette here or anything.