I understood explanations from @Daimona, but this comment to let know that this feature is still needed (we got vandals who edit undo summaries to bypass AF). Being able to detect built-in tags, such as mw-undo, with AF would be great.

Thanks for the fix!

It doesn't work with safemode either.

Thanks for the info to both of you!

Hi @alexhollender_WMF. Dec 2 2022 you gave useful CSS to enable TOC numerotation. It doesn't work anymore. Do you know how to make it work again? Best.

Ok, thanks!

Ok, it's a duplicate of T332994 and can be closed.

Yes, it works again. Thanks!

Near the same: clicking the blue access-button, it says: "Should you have institutional access? Here's how to get it ..." on a yellow background. And I don't have access to restricted contents anymore.

+1 MarcoAurelio. I always found the name hideuser very confusing. (Same for Abusefilters logs suppress right, which is named abusefilter-hide-log…)

FYI, if that can help, @Od1n created a Javascript code that makes the Abusefilter edit window resizable.

Hi. Enumerations in the new ToC has been requested on fr-wp Village pump (for example there and there). As the new ToC was criticised by several wikipedians, it was said to them that the lack of enumeration was taken into account . As there is a CSS code that works, I don't understand why it's not implemented as a clean option (for editors not familiar with using CSS). Best.

Similar bug reported on fr-wp.

Thanks. Imho, page_last_edit_age , aka seconds since last edit on page, would be fine. Ok for your second point, it seems logic to me; so we will always have to use page_last_edit_age != "null" (or page_age > 0? that should work too if I'm correct, but it is less explict).

This is very much needed; there have been several times where it would have been very helpful, in particular against harassment/houding by LTA.

Thanks @Msz2001!

On fr-wp, there are 19 scripts impacted, including one very useful for patrolling/reverting. Should we fix it locally (how?), or will this bug be fixed globally?

In T299653#7637063, @Aklapper wrote:

Hi @Jules78120, thanks for taking the time to report this! This happens because https://fr.wikipedia.org/wiki/MediaWiki:Common.css defines text-align: justify; for .messagebox and needs to be brought up and fixed on the local wiki by the local community instead.

Thanks @Billinghurst, I will keep in mind this possibility.

@Supertoff There was a line 28 in the version of the filter used at the time those accounts have been created, see the link in the description I wrote above. See also the email on which you are in CC ;)

Error is mine, sorry (see parameters of the filter).

Thank you for your reply @Daimona. I opened a new ticket, T290324; I understand that it will not be worked on quiet soon.

What's the meaning of "user-agent" in this context?

Sorry, I'm tired, I meant "variable", not "user-agent variable" (don't know why I wrote that ><). I changed the title.

We recently encoutered a case of doxing of several Wikipedians on fr-wp, which led us to hope for CU and/or OS level abusefilters: CU for a future user agent variable (T50623); OS to filter real names of Wikipedians with better privacy.
Should I open a new ticket for OS-level abusefilters, or should it be added to this ticket?

This is much needed: on fr-wp, for example, we have a couple of banned people harassing volunteers by reverting their edits. And there is no efficient and clean way to handle that currently with AF.

I second the request.

Even if no block was visible, I tried to unblock the IP adress and it worked (a message saying that the IP was unblocked displayed), so I could then block it again. But this doesn't explain why there was a previous invisible block.

This time, I doublechecked and found that the source of the bug is https://fr.wikipedia.org/wiki/Utilisateur:Arkanosis/xpatrol.js

Okay, I take it back: it was not the source of the bug. After removing the script, the bug is still there.

@Daimona Thank you very much for you help. I found the script causing the bug: [[Utilisateur:0x010C/script/EnhancedContribToolList.js ]]. It's an Uncaught TypeError: mw.Api is not a constructor. I removed this script from my .js. Only one other user has this script enabled, I will warn him.

@Daimona Thanks for the reply. I tried with &safemode=1: indeed, the bug does not appear anymore. I will try to find what .js or .css can cause that.

When the menu does open, the parameters drop-down ("Toutes les actions", "Tous", etc.) don't open; they seem to be affected by the same bug.

Sometimes the menu does open, but can't be closed.

Good idea. I wanted to test the Newcomers homepage feature, spent five minutes searching in my settings how to enable it, didn't found, had to ask to someone else... Would be easier with the feature Trizek suggests.

I think it's OK @Urbanecm. (But the "e" of "libre" is cut.)

Probably linked to T262234. But if I understand the explanation by @Samwalton9:

We follow Twitter's specification for what constitutes a hashtag, which includes not flagging it if there is no space or punctuation before the hashtag

Thanks.

I understand what you say. But consider that having to use a lot of energy and time to fight banned users (and especially when there is harassment or something close) is exhausting.

If being banned from fr-wp and using a blog to harass is not sufficient (…), I will indeed create a discussion on fr.wp. I don't mean to be rude, but this is non-sense.

I think the link already in the description pointing to the Sockpupett investigation is sufficient https://fr.wikipedia.org/wiki/Wikip%C3%A9dia:Faux-nez/Maitreidmry, as the user is banned and uses this blog to harass another Wikipedian.

Thanks @Aklapper for the info! I will take a look, but I think it's a bit complicated for me (I never used Gerrit).

Same problem on frwiki: edits on Flow talkpages do not show in Abusefilter Testing Tool.