In T366127#10014214, @Cyndymediawiksim wrote:

@JFernandez-WMF , @KStoller-WMF , as a reviewer suggested on this patch uploaded for this task: Hooks: change wikipedia is made for you warning to a notice message, he suggests moving this specific piece of code from the MinervaNeue skin, into MediaWiki core. Would the specific notice/warning behavior be universally beneficial across all MediaWiki use cases?

In T370177#10001571, @DMburugu wrote:

@Sgs On the point regarding: Compare the current homepage module schema with the core schema fragments provided by MP to surface unavailable "features" I assume this will entail listing limitations for future consideration but we're not going to let any disparity we note stop us from using the core schema fragments right? At the very least, we can progress with what's available in the Core Schema fragments.

Thanks for reporting.

My perception is that the issue has always been present in chip input controls.

I agree it can lead to confusion, what happens is that they get the "enrollasmentor" permission but they are not directly enrolled. Maybe just updating to are to can be. What do you think? cc @Urbanecm_WMF @KStoller-WMF

@Nikerabbit is this something the language team is gonna be able to work in any time soon? We could try to do a temporary fix in GrowthExperiments if that's not the case.

Since T368160 we also have field descriptions, I would suggest to also allow links there.

In T365885#9982140, @KStoller-WMF wrote:

My understanding is that the fallback thumbnail should display if there is a problem loading the image added via Community Configuration and also if there is not an image / logo added via Community Configuration.

Ack.

There are some scenarios where extensions (namely GE) remove the warning. For instance, GE removes it when the page is rendered for a campaign. If we change the warning to notice, should we also remove it in those situations, or on the contrary, the message can remain? @KStoller-WMF @JFernandez-WMF

Is the fallback thumbnail supposed to show when there's a problem loading a set logo or always, even if no logo was provided by the configuration? @JFernandez-WMF @KStoller-WMF

Since the minimum cap is already implemented I think we can move forward with it for the MVP and seek feedback from campaign and event organizers.

What to do if it is a nested field? Show all labels? With what separator? word-separator-message (usually a space)?