My conscious is a jukebox
User Details
- User Since
- Dec 14 2014, 11:39 PM (515 w, 4 d)
- Availability
- Available
- IRC Nick
- musikanimal
- LDAP User
- MusikAnimal
- MediaWiki User
- MusikAnimal [ Global Accounts ]
Yesterday
I was able to repro in Chromium. Also, at full speed (no throttling). This is a must-fix issue.
Nope! The "Another way" repro steps is still a problem. I'm not done here yet.
Passing this back to Dom for QA. I am hoping the change made to fix this may help with some of the other issues identified at T357482.
The v6 module loads the CodeMirror lib (ext.CodeMirror.v6.lib) at the same time as the visualeditor module. In v5, it is loaded after VE and the toolbar have loaded. I'm fairly sure that's the problem. It may have something to do with the fact that ext.CodeMirror.v6 needs the library upfront, while ext.CodeMirror does not. Simply adjusting extension.json (adding ext.CodeMirror.v6.lib as a dependency, etc.) and even adding some mw.loader.using() blocks doesn't seem to reliably fix the issue.
Wed, Oct 30
I got the acceptance criteria wrong. My mistake!! The messaging shown in the screenshots is correct. The "hard block" option as it's sometimes called is actually two different messages, depending on if you're blocking an IP or account.
Tue, Oct 29
I've tagged the components that this app may potentially be part of. If any maintainers or teams disagree and feel this doesn't belong in said component, please feel free to remove the tag(s).
Thu, Oct 24
Done! Examples:
Wed, Oct 23
Users should be able to filter wishes by category by typing in the filter or selecting from a dropdown.
Tue, Oct 22
I think we came up with a means to test it at https://wikimedia.slack.com/archives/C05QYAMAV4G/p1729526567836379 – where I said:
❓ Possible Issue
When you go to Special:Block/BlockedUser, replacing BlockedUser with the appropriate username (ex. Betatester), did you want the Backl og to automatically open, since it's specific to that username or do you want to manually click on the Block log to reveal the log as seen in the gif
I'll be bold and resolve this. Outstanding issues are captured in other tasks.
Being bold and moving this back to QA, as I think we're seeing the expected behaviour.
From the repro steps: