@Zoranzoki21 could you specify what exactly is missing? Do you mean that some content is missing, or just a border around some controls.

If I get it right, the only missing part is the border/box around "Edit", "Move" and "Pending Changes" controls, on mobile everything looks like one form that has no separation, just all controls one below another. Am I right?
(and the second missing part, the confirmation on successful action).

In T235424#5574878, @pmiazga wrote:

@Zoranzoki21 could you specify what exactly is missing? Do you mean that some content is missing, or just a border around some controls.

If I get it right, the only missing part is the border/box around "Edit", "Move" and "Pending Changes" controls, on mobile everything looks like one form that has no separation, just all controls one below another. Am I right?
(and the second missing part, the confirmation on successful action).

I mean on border. Confirmation too, you are right.

/cc @alexhollender @ovasileva this is most probably something we can do under the AMC work, not sure if we have time for it.

@Volker_E looks like this needs OOUI... This page has a lot of problems. Page issues is also running on this page.

Couldn't find any mention of this interface view as part of T100161: Convert all of MediaWiki core to OOUI PHP (tracking)…?!

Btw, why non-admins can access to action=protect? It should show just a warning. No and warning and options. Is it expected behaviour?

Change 545417 had a related patch set uploaded (by Jdlrobson; owner: Jdlrobson):
[mediawiki/core@master] WIP: Protection form built in OOUI

https://gerrit.wikimedia.org/r/545417

Change 545417 abandoned by Jdlrobson:
WIP: Protection form built in OOUI

Reason:
Not working on this for now. Conversation will continue on phab ticket.

https://gerrit.wikimedia.org/r/545417

In T235424#5597155, @Jdlrobson wrote:

• Why are the fieldset labels not translating properly?!

Because the messagePrefix is set to an empty string, but HTMLForm is still adding the dash (see T248063). The solution is to use restriction as the prefix (4th parameter of HTMLForm::factory) and to not add restriction- to $section.

Change 581878 had a related patch set uploaded (by BrandonXLF; owner: BrandonXLF):
[mediawiki/core@master] Use OOUI for protection form

https://gerrit.wikimedia.org/r/581878

I tested patch on my test wiki.

Just to note, I changed zoom to be 90% so everything can fit in the screenshot.
Design looks good for me, but for "Other time" maybe we should make it like "Expiration" on Special:Block.

Before:

After:

The create fieldset styling seems problematic to me. Should there be an indent or margin here or some kind of messaging under confirm protection @Volker_E ?

We could consider doing away with the extra indentation and all, but the bottom border for the fieldset > fieldset…?

In T235424#5988784, @Kizule wrote:

Design looks good for me, but for "Other time" maybe we should make it like "Expiration" on Special:Block.

Agreed - is this easy to re-use?

The issue is that when "infinite" is selected (or any of the options in the dropdown) the other textbox is hidden, making it harder to set a custom expiry and making it so the input is only half the width of the form.

In T235424#6771002, @BrandonXLF wrote:

The issue is that when "infinite" is selected (or any of the options in the dropdown) the other textbox is hidden, making it harder to set a custom expiry and making it so the input is only half the width of the form.

Are this issues specific to this use case, or general issues you have with the widget? Are custom expirations more likely on unprotect vs block?

Unlike the block form, the protect form has "infinite" selected by default whereas the block form has "other" selected, meaning the other textbox is immediately visible on the block form but it wouldn't be if the widget was used on the protect form.

Current look:

I still think this:

Design looks good for me, but for "Other time" maybe we should make it like "Expiration" on Special:Block.

You can use https://srwiki-dev.wmcloud.org for testing if needed.

On my Honor 8A phone with Microsoft Edge 45.12.2.5137 looks good too.

Change 581878 merged by jenkins-bot:
[mediawiki/core@master] Use OOUI for protection form

https://gerrit.wikimedia.org/r/581878

Patch was merged

Not sure if it's related to ?action=protect or Pending changes, but the pending changes part of https://en.wikipedia.beta.wmflabs.org/wiki/Main_Page?action=protect isn't in OOUI.

In T235424#6820561, @TerraCodes wrote:

Not sure if it's related to ?action=protect or Pending changes, but the pending changes part of https://en.wikipedia.beta.wmflabs.org/wiki/Main_Page?action=protect isn't in OOUI.

That is covered by the child task T236218.

In T235424#6820561, @TerraCodes wrote:

Not sure if it's related to ?action=protect or Pending changes, but the pending changes part of https://en.wikipedia.beta.wmflabs.org/wiki/Main_Page?action=protect isn't in OOUI.

Ah, thanks.

Can no longer prefill the mwProtect-reason input field. Prefilling the mwProtect-edit-expires input field populates both the fields with the same value instead.

Also, prefilling mwProtect-level-move checks the mwProtect-cascade checkbox for some reason, while prefilling any value checks the mwProtectUnchained checkbox.

@Sakretsu: Hi, please file a separate follow-up task. Thanks a lot.

T274980: Protect Page form leaves the Watch page checkbox unfilled leading to unwatching the page on protect might also be a potential regression from this.

Change 705130 had a related patch set uploaded (by DannyS712; author: DannyS712):

[mediawiki/core@master] Remove the `mediawiki.legacy.protect` ResourceLoader module

https://gerrit.wikimedia.org/r/705130

Change 705130 merged by jenkins-bot:

[mediawiki/core@master] Remove the 'mediawiki.legacy.protect' ResourceLoader module

https://gerrit.wikimedia.org/r/705130