User talk:Alexis Jazz/Factotum
Archives
|
![]() | Due to personal issues, Alexis Jazz will be away from Wikipedia for an undefined period of time. |
Can't undo pastesEdit
Hello! It's been a while since I've been here. After we finished turning Factotum into a gadget for SqWiki, I decided to take a wikibreak and then my laptop broke down and then I had problems with 2FA on the new device which were finally resolved today. I just noticed that I can't undo my pastes with Factotum. Given that a lot of time has passed I'm not sure if that is a known issue or not. They don't get detected at all because even the undo arrow stays grey.
Given that I have the option to get Javascript error notices on and that the kitty always invites me to report any new general error here, I'll continue to do so just to have a list for anyone interested or even you on a future time. I don't expect a fast answer/fix on them. I'm saying all this in regard to your user page notice about personal issues. Feel free to ignore these until you find time to deal with them. I must say that these cases are rather rare though. As I said, I returned to Wikipedia today after more than a month and I had forgotten how good Factotum really was. I was doing things thinking to myself "Imma try this but there is no way this button also works like this" and it always turned out it did! It felt as I was neurolinking it. I hope you're enjoying your time and have a good end of year! — Klein Muçi (talk) 12:23, 9 December 2022 (UTC)
- @Klein Muçi, works for me. — Qwerfjkltalk 11:30, 10 December 2022 (UTC)
- Qwerfjkl, I was wrong about the arrow staying grey. It doesn't and it works with it. But Ctrl+Z doesn't work. — Klein Muçi (talk) 12:57, 10 December 2022 (UTC)
- Klein Muçi, thanks for the kind words. The whole undo/redo thing can be flaky at times, but I'm not spending much time here at all. Maybe some other developer will pick things up one day, maybe not. — Alexis Jazz (talk or ping me) 01:30, 7 January 2023 (UTC)
- Alexis Jazz, yes, no problem. Considering the
Maybe some other developer will pick things up one day, maybe not.
part, wouldn't notifying at WP:US be a good choice? Something like "setting it up for adoption" or asking for more help in dealing with requests such as ours given that you don't have enough time to solve them yourself currently? — Klein Muçi (talk) 12:07, 8 January 2023 (UTC)- Klein Muçi, it's WTFPL, anyone can fork if they want. You don't need my permission. If they want to keep the name they should probably ask to avoid the confusion of different scripts with the same name.
It's not reasonable to make such requests for scripts with only a handful of users. It's rare for anyone to adopt a project as the creator is always the most familiar with it. It's often easier to start from scratch. — Alexis Jazz (talk or ping me) 23:34, 8 January 2023 (UTC)- Alexis Jazz, I understand you point of view. I was mostly hoping for any choice that wouldn't "introduce a lot of new chaos in the system". Multiple forks would make things a bit harder for projects such as SqWiki which ultimately stay reliant on you/EnWiki for its gadget. We only have one version currently and already they've become unsychronized, given that you just updated the script lately (which I will do now) and because I suppose you're yet to update the translations in here. Imagine having multiple versions simultaneously and maybe none of them caring for "others needs" (a rather dark depiction of Wikipedia). I suppose the problem per se is mostly related to the fact that interface admins aside, scripts can only be updated by 1 person only, their creator. As for
It's not reasonable to make such requests for scripts with only a handful of users
... I would think that asking for help and cooperation in dealing with Wiki-requests when you're experiencing personal issues is reasonable - at least I've asked for help in less related things and more often than not I've found a welcoming environment here - but I also understand that usually things aren't as simple in practice.
I hope things get better in the future. Take care! — Klein Muçi (talk) 00:42, 12 January 2023 (UTC)
- Alexis Jazz, I understand you point of view. I was mostly hoping for any choice that wouldn't "introduce a lot of new chaos in the system". Multiple forks would make things a bit harder for projects such as SqWiki which ultimately stay reliant on you/EnWiki for its gadget. We only have one version currently and already they've become unsychronized, given that you just updated the script lately (which I will do now) and because I suppose you're yet to update the translations in here. Imagine having multiple versions simultaneously and maybe none of them caring for "others needs" (a rather dark depiction of Wikipedia). I suppose the problem per se is mostly related to the fact that interface admins aside, scripts can only be updated by 1 person only, their creator. As for
- Klein Muçi, it's WTFPL, anyone can fork if they want. You don't need my permission. If they want to keep the name they should probably ask to avoid the confusion of different scripts with the same name.
- Alexis Jazz, yes, no problem. Considering the
Icons appear cut in half in SqWikiEdit
Klein Muçi (talk) 13:10, 10 December 2022 (UTC)
- @Klein Muçi, this was fixed here with this edit. — Qwerfjkltalk 14:39, 10 December 2022 (UTC)
- @Qwerfjkl, I had forgotten that SqWiki is using its own version of code since we set it up as a gadget. Updated accordingly and it was fixed. Thank you!
PS:Factotum-Extra needs a little update in Albanian translations apparently. — Klein Muçi (talk) 17:24, 10 December 2022 (UTC)
- @Qwerfjkl, I had forgotten that SqWiki is using its own version of code since we set it up as a gadget. Updated accordingly and it was fixed. Thank you!
Feature requestEdit
When using mentions, links and tags, when the cursor is located at the limit of the mention/link/tag (beginning or end), hitting the up/down keys sends it to the beginning/ending of the mention or pairing bracket/tag instead of the usual behavior when it just goes to the absolute beginning/ending of the text box. - Klein Muçi (talk) 13:45, 10 December 2022 (UTC)
- Klein Muçi, same as below, personal issues. No plans to look at this. — Alexis Jazz (talk or ping me) 01:26, 7 January 2023 (UTC)
Bug reportEdit
When using the dropdown list of mentions or link insertions, the undo/redo, text formatting, mention and link insertion buttons get shown above the dropdown list. They should instead disappear (or "shown below it") like the magnifying glass, warning sign, arrows and cog buttons do. Also using the scroll wheel on such dropdown lists is pretty chaotic. Sometimes the command acts on the whole page itself, sometimes only on the dropdown list and most of the time it acts on both the page and the dropdown list simultaneously. — Klein Muçi (talk) 18:02, 10 December 2022 (UTC)
- Klein Muçi, as personal issues remain, I have no plans to look at this. But it sounds like at least half of what you're complaining about is browser (or in some cases MediaWiki) behavior. I have limited control over MediaWiki dropdown lists and zero control over browser dropdown lists. — Alexis Jazz (talk or ping me) 01:24, 7 January 2023 (UTC)
Major bugEdit
@Alexis Jazz, there is no urgent need to fix this bug. It's been around for a while and doesn't particularly bother me. That being said, it does prevent me editing references, which is a very useful feature.
When I try to edit references (using the edit symbol next to the reference), the selectRange() bug prevents me from doing so. — Qwerfjkltalk 09:36, 15 December 2022 (UTC)
- Qwerfjkl, I wouldn't call that a "major" bug. No data loss, doesn't prevent you from reading any page. As I said below, personal issues remain. Working on this doesn't make me happy and this particular issue may or may not be an easy fix. I have no plans to work on this issue. Sorry. — Alexis Jazz (talk or ping me) 01:20, 7 January 2023 (UTC)
Link autoconversion fails when formatting is introducedEdit
I was trying to italicize a link by surrounding it in double singular quotes and the autoconversion magic stopped happening, switching the link back to its absolute URL form (instead of it being an internal wikilink). Can the said magic be upgraded to understand such formatting? - Klein Muçi (talk) 13:14, 3 January 2023 (UTC)
- Klein Muçi, links that fail to convert are preferable over links that shouldn't have been converted but are converted anyway.
Could the magic be upgraded? Probably. Would that be safe? No idea. Am I going to try and do this? Nope! That personal issues thing remains ongoing. — Alexis Jazz (talk or ping me) 01:07, 7 January 2023 (UTC)
Subscribe bell on Wikipedia namespaceEdit
I get the subscribe bell on all (?) pages in WP-NS. Is that "normal"? You can try it on WP:PetScan as an example. — Klein Muçi (talk) 17:09, 6 January 2023 (UTC)
- Klein Muçi, a common problem of MediaWiki/Wikipedia: page types aren't indicated anywhere. WP: is a signature namespace, so it COULD be a talk page. No way to know! Take phab:T249293 for example where a similar problem is caused by the fact that discussion archive pages can't automatically be identified as such. And in the past I had issues with {{Automatically generated}} not existing to indicate lists that are maintained by (semi-)automatic processes.
WP:PetScan might be a talk page - no way to know. — Alexis Jazz (talk or ping me) 01:13, 7 January 2023 (UTC)
Small bugEdit
Alexis Jazz, you messed up! (possibly)
Replylinkparams:
{"int":1419,"type":"comment","subtype":"legacy","id":"Moops:20:44, 6 January 2023 (UTC):1419","pageTitleInt":1401,"origReplyTo":"Moops","origTimestamp":"20:44, 6 January 2023 (UTC)","origTimestampTextNode":"20:44, 6 January 2023 (UTC)","seq":0,"origReplyToUnderscore":"Moops","pageTitle":"User talk:Moops","sectionTitle":"Your talk page","sectionseq":0}
Page: [1]
Active editor: source
Page loaded at: 10/01/2023, 17:02:16
Error occured at: 10/01/2023, 17:12:30 UTC
My settings:
{"replySecLink":true,"nSecLink":false,"inputBoxTO":false,"editFullPage":false,"editRefs":false,"thankLink":true,"dateLinksLocalTime":true,"dateLinksLocalTimeRelative":true,"dateLinksLocalTime12H":true,"dateLinksLocalTimeWeekday":true,"tosNag":false,"markup":false,"redoBtn":true,"pingDropDownAt":false,"onetimetoolsBlock":false,"noticeNeverPopup":true,"previewBtns":"pbDisabled","UIfontSize":"medium","customSummary":true,"livePreviewCmt":false,"aggressiveLivePreview":true,"AWBtypos":true,"cI":[""],"cIThatRun":["%2F---%2F%E2%80%94%2Fg"],"cIThatRunCmt":[""],"pingText":"{{ping|PINGUSER}} ","pingTextInSection":"{{ping|PINGUSER}} ","markNewCmtsSubbed":false,"showUnpopular":true,"showRisky":true,"showSuperRisky":true,"hideDTSub":false,"extendedSigDetect":true,"autoDash":false,"RLmasq":true,"blacklistMain":true,"livePreview":true}
Skin: vector
# of .BawlLinks: 146
# of elements processed: 1566
Element types processed: H1, TD, P, LI, SPAN, DD, SMALL, I, S
Additional information: Tiny thing: the "m" checkbox for minor edits is not on the topmost layer. I was at User talk:Moops (which has a teacup in the bottom right corner) and only the m was being covered by the teacup.
HouseBlastertalk 17:17, 10 January 2023 (UTC)
- HouseBlaster, m should be above the tea cup now. — Alexis Jazz (talk or ping me) 23:21, 10 January 2023 (UTC)
- @Alexis Jazz: Tysm! Alexis, I sincerely hope things get better for you soon. Best, HouseBlastertalk 00:49, 11 January 2023 (UTC)
Factotum doesn't understand unsigned-botsigned commentsEdit
I was trying to reply to a comment on Meta and I didn't get the reply button from Factotum. The comment had been left unsigned by the user and was later "signed" by a bot with the traditional The preceding unsigned comment was added by... Any hope for Factotum to understand such comments as comments? - Klein Muçi (talk) 11:17, 20 February 2023 (UTC)