Mon, Dec 17
Thu, Dec 13
Mon, Dec 10
Fri, Dec 7
Wed, Dec 5
This appears to happen because the input widget inside the titles multiselect widget is wider than the max width of the titles multiselect widget at first.
Are we planning to reinstate this once T211048 is resolved?
Just pointing to T211048, where we're auditing the affected classes - any feedback very welcome!
This is affecting the TitlesMultiSelectWidget on Special:Block too (with partial blocks enabled).
Tue, Dec 4
Unless @dmaza disagrees, I don't think any of these options should be particularly complex.
I've updated the list of classes that don't explicitly override requiresUnblock to state the return value that they inherit (see above).
Mon, Dec 3
@Anomie Good point. searching "extends.*<className>" throws up one more result (PurgeAction in Flow) - updated the list above.
- Search: https://codesearch.wmflabs.org/search/?q=requiresUnblock&i=nope&files=&repos=
- For each class where requiresUnblock returns false, search "extends <className>"; do this iteratively for all descendants until no more results
Fri, Nov 30
This also affects sitewide blocks in the same way.
Wed, Nov 28
@Ryasmeen Oops looks like I forgot to push the change - thanks for pointing that out!
Tue, Nov 27
Here are some screenshots in the different skins with that patch:
Mon, Nov 26
Special:ActiveUsers task filed as T210391
Fri, Nov 23
Do we want to do the same for Special:ActiveUsers?
Wed, Nov 21
It seems there are two points at which we need to show the loading bar:
- while the JS widget is loading, if the user has JS
- while the menu is loading, after the input has been changed
Tue, Nov 20
Mon, Nov 19
Looks like this isn't actually an exact matching problem, or anything affecting 1-character titles exclusively.
Nov 16 2018
Nov 15 2018
Nov 14 2018
Nov 13 2018
Nov 12 2018
Nov 9 2018
Nov 8 2018
Nov 7 2018
Nov 4 2018
Oct 29 2018
@Ryasmeen Is it possible you're looking at inspectors? The extension dialogs are graph, math, chem, maps, syntax highlight and pre. These and other dialogs should all have "Apply changes" - do you see those?
Oct 15 2018
Oct 10 2018
Thanks for the feedback.
Oct 9 2018
Oct 8 2018
Oct 4 2018
With the narrower inputs, there's no wrapping on a 320px-wide screen, and 4-digit numbers fit comfortably.
Oct 3 2018
While looking into this, I noticed the spacing between elements is affected by whether we have fieldset->widget or fieldset->field->widget. It's also affected by whether we use addItems() or append one element to the other. We should use these components properly to get a predictable appearance, and if there's a need to deviate, we should comment why.
Thinking more about point (4), that layout looks pretty crowded on a mobile screen: