Why is it bad design? Because as soon as
— the table gets narrower,
— or the block reasons (3rd column) get longer,
— or there are more block parameters (2nd),
the entire page becomes horribly structured. There is no reason for table here, as no one would have even just 5 active blocks.

The solution? Create a new component to display this info in a readable, adaptive design instead of using a badly fitting one.

UI standardisation is pointless if it doesn’t produce a good interface.

Don’t get me wrong, I think having a design system is long overdue and a completely good development for MediaWiki. However, the lead for the project took this screenshot and didn’t even ask the obvious question ‘Should this really use a table when it looks so shit?’

And this is where WMF and MediaWiki are going horribly wrong with Codex at the moment.

@LucasWerkmeister I actually love it (since it allows to switch between search engines easily) but maybe it’s because I don’t use a separate search bar like many do.

You can press Esc twice to get to the actual URL when that’s needed.

@cscott @LucasWerkmeister ideally there should be some sort of mechanism of global feedback on such things, rather than no feedback, however.

Even in that example some communities might be more affected by this than others (real hypothetical for ruWP in that case would be ‘drawing big attention to the fact FancyCat72 last edited the page could inadvertently put them in danger’).