Just to inform that maybe a sub-task bug report will be created soon. Related discussion: https://phabricator.wikimedia.org/T333885#9132176

(I accepted but before landing please first review all not-done inline comments: https://we.phorge.it/differential/revision/inlines/25420/ and this comment: https://we.phorge.it/D25420#12264 )

In D25420#12264, @waldyrious wrote:

I like this approach, and prefer it to my simpler attempt from D25426; but have some minor suggestions:

• Instead of "You can ignore this conflict or adjust your profile setting to match your client", we should use the same order in the sentence as the options are shown to the user: "You can adjust your profile setting to match your client, or ignore this conflict."
• The label for the checkbox should be just "Ignore Conflict", without the "Or" at the start.
• When the "Ignore Conflict" checkbox is selected, the timezone dropdown should be disabled (and re-enabled if the checkbox is unmarked)

Yeah, that's nice! Though I'd replace the ! at the end with a :, and would remove the horizontal ruler (while keeping the new paragraph for the we.phorge.it link). This way it is clear that the last line is a continuation of the previous one; otherwise, it may not be immediately clear how one is supposed to "join the community".

In D25425#12230, @valerio.bozzolan wrote:

maybe in the future we can have a CSS selector to be applied just to the "phorge/" pathname, in order to avoid mouse selection, and select just the command.

In D25426#12221, @avivey wrote:

See D25420 for a conflicting change...

I like this approach, and prefer it to my simpler attempt from D25426; but have some minor suggestions:

Check out https://we.phorge.it/book/contrib/article/javascript_coding_standards/ and the Javeline docs here: https://github.com/phacility/javelin/tree/master/src/docs/concepts
(I'll try to render the Javeline guide here later).

Sorry, I mean this link:

I absolutely don't know what we are doing here since I don't know the supposed "Phabricator way" to interact with the DOM via JavaScript using its library.

Screenshot from:

We were able to push Phorge subliminal messages in an official Wikimedia video \o/

Yeah thanks! Maybe we can somehow keep the footer, in order to have a link for people like me that just have their brain switched-off and just look at the bottom link. Also maybe we can simplify a little bit.

Thanks for this patch. Yeah if I understand correctly, this should work:

I'm Valerio, a simple person: I see "GNU/Linux" and I say "yeah, land".

See D25420 for a conflicting change...

ooh, check out D25349 for basically this exact use-case...

IMO the added text should be connected to the second sentence of the existing third paragraph, maybe as a separate paragraph. In fact I'd suggest re-grouping the paragraphs differently, to focus on a brief intro, info for users, and info for contributors. Perhaps something like this:

@valerio.bozzolan I found the js section where with the listener for open/close the persistent chat. From there I can get element somehow (by ID I don't think it would be good, because it seems to be auto-generated (UQ3_0)) and remove the class "core-menu-item" and the invisible gear icon will no longer be clickable. If the chat is not minimized, we add the class back so we can see it and click it.

cosmetic whitespace changes

Updating D25420:

This is very promising. Just added an inline comment

if you check the checkbox, it will use the current setting timezone.

Updating D25420: Updating D25420: fixed tests error

Updating D25420: Added a checkbox to ignore timezone conflict in Adjust Timezone dialog window. Using the checkbox instead of a button because this way it's possible to reuse the existing form. Also, i still didn't find a way to capture the additional button click event. This way, if you check the checkbox, it will use the current setting timezone.

This is very probably a recent regression since I cannot reproduce on Wikimedia Phabricator.

Looks good

Looks good to me.

This happens also with the Upload File dialog

Ah! I can reproduce exactly in this comment!

Finally, after additional tests, I guess these issue are not related (as related in T15629)

consider more cases