**Feature summary** (what you would like to be able to do and where):
Since the new block form uses Codex, and Codex appears to require JavaScript at this time, if JavaScript is not enabled, and both `$wgUseCodexSpecialBlock = true;` and `$wgEnableMultiBlocks = true;` are present on LocalSettings.php the block form is unusable. Likewise, if `$wgUseCodexSpecialBlock = false;` (the feature flag which will eventually be removed) then it is impossible to issue multiblocks.
{F71371505}
The old OOUI block form should continue to be available and should also support multiblocks without Codex. This could be done by adding a list of all active blocks with their block IDs to Special:Block and Special:Unblock when Codex is not enabled, and allowing a user to select a block when blocking or unblocking.
On Special:Block, we can provide a warning that a new block will be created unless if a block ID is specified in the username field, in which case the block will be modified instead. On Special:Unblock, we can provide a warning that typing a username into the unblock field will remove ALL blocks associated with that user, while typing a block ID will remove only the block associated with that block ID.
**Use case(s)** (list the steps that you performed to discover that problem, and describe the actual underlying problem which you want to solve. Do not describe only a solution):
1. I disable JavaScript.
2. I visit Special:Block or Special:Unblock.
3. I get the above notice that JavaScript is required.
**Benefits** (why should this be implemented?):
The benefit is to provide a way to use the block form when JavaScript is not enabled or supported. For example one may want to disable JavaScript when editing from a low end machine for improved browser performance.