@eranroz, would you like to review the patch?

I see, my fault. Thank you.

In T210496#4777675, @Agabi10 wrote:

It can't be added until the change is deployed. If added before it's considered normal text, not a magic word.

Not until this moment. I think you can make it stalled for now.

@Addshore?

Thank you. I also thought this can be the reason, but it's too confusing, indeed. New message is a good idea.

I believe you are right. Something missing. I'll try to reproduce. Or, possibly, it was already fixed unintentionally.

That was I saw in "computed" panel in Firefox.

Well, it works. I found the problem. Thank you for your help. The problem was that when I changed the name of message, and then choosed "another message" in the popup menu, it returned to "abusefilter-disallowed", probably as a browser bug, so I edited the wrong message. So, (A) can be closed as invalid. I still do not know why did I see the double message in (B), but I can't reproduce it any more. Maybe it was has something with (A), still I can't understand how is it possible. Or some system glich. Anyway, I'm closing the task as invalid now, and if (B) will return, I'll reopen it. Thanks again.

Actually, @Daimona, I gave you all that I have. If the problem is on my side, I do not see it.
I can't provide such a flag. Let's ask @eranroz.

What info do you need, @Daimona?

In T136104#4674572, @Charlie_WMDE wrote:

Can I ask you what concern you have with displaying the year at all times? If it interferes with an existing workflow or we have not thought of an edge case where it would cause problems, I'd love to hear about it!

I see. A pity. Thank you.

In T136104#4674250, @Charlie_WMDE wrote:

You could say: but when the people hover over a revision they'll see the year immediately

No, I can't, because of mobiles. But I can say: everyone sees the tool for the first time only once in their life. In all the rest uses they already know how does it work.

Just a question. Sorry if it was already asked. Why do we need at all the current year? What's wrong in "Apr 17 - Oct 17 - Apr - Oct"?

As far as I know, it's on many browsers. Quantum. And F5 is not an issue here, you can open another wiki page instead.

Thanks to @eranroz for calling me. Well, I think it can be very useful feature. But for me, soft redirect isn't the main issue, but tracking categories. There are thousands that we try to keep emptied, and removing them from the special page will be very helpful. About the list of excluded categories, excluded and empty categories, or excluded and non empty categories - I do not really care, because I can use query. But on large wikis it can't cope with this, so these lists can help too.

I see. @Amire80?

Non text - you mean wikilink?

I do not sure it is possible. I can tell that if I open now local prefs and change this, I'll see it back in a while. But I do not know how to reproduce the start situation, so it begin to happen.

In T204226#4591005, @Framawiki wrote:

Patch merged and deployed, but the problem is not totally solved as said in previous comment. We haven't any idea/can't do anything to resolve your exact problem.

Thank you.

X is "auto-hyphenation can hyphenate here, and it's wrong"
V is "it should be hyphenated only here"
X is "auto-hyphenation can hyphenate here, and it's very wrong"
V is "auto-hyphenation can't hyphenate here, and it's wrong"

SuXperVcaXliVfraXgiVliXstiXcVexXpiVaXliVdoXciXoXus

Sure. And also, there are words where you want to hyphenate in places you decided, not the auto-hyphenation mechanism. So adding this manually will be very helpful.

In T85847#4587104, @Xaosflux wrote:

This shouldn't be blocking using templatestyles, when creating a new template style (e.g. https://test.wikipedia.org/wiki/Template:389573/styles.css) is is already in the correct content model.

Sorry, I do not understand how can it help.

I'm not following why developers would be refusing to allow access to communities that have specifically reviewed and requested access for certain groups though? Do you have the phab numbers to review?

Of course, here you are: T188287, T187729. And also https://he.wikipedia.org/wiki/Special:AbuseFilter/90 and https://ru.wikipedia.org/wiki/Special:AbuseFilter/168.

In T85847#4586773, @MGChecker wrote:

Seems like a nice to have feature to me, but you can just change it back if abused? Changing content models is even easier to revert than page moves (because of the redirects).

If it will be done, is there a way to avoid contentmodel change from something to sanitized css, using abusefilter?

As you suggested, without the parameter. It is not urgent know, because you solved the problem with encoding, but maybe you can thing about it. And also about the warning I mentioned. Thank you.

Still, you can add one more option.

Honestly, I would prefer just get rid if this ?download=true and leave the url as https://quarry.wmflabs.org/run/290198/output/0/html, which works fine despite having the exact same binary contents.

Great idea.

Very well. Yes.

Very well.

Hi, @zhuyifei1999, and thank you. Could you please add an explanation somewhere in the output?

N3: About you asked: Last Quantum on Windows 7.

I understand your problem. Usually it's OK. But now the bug report goes to one particular person, that know all that. Here is your link: https://quarry.wmflabs.org/run/290198/output/0/html?download=true.

I do not see what to write here, but here you are:

1. Run 27365.
2. Check html output.

Thanks for calling me, but I'm the wrong person to ask this - I do not work with this wizard.
But I agree you should not spend your time on wikEd compatibility. The wikEd gadget has a lot of problems, and I see many complains that it destroys either interface or pages wikicode. Avoiding common work of these two tools is indeed a good idea.

Great, thanks.

In T201340#4557039, @Mooeypoo wrote:

Are you changing any of the local or globals and not see them as what they should be?

Yes, it is so. I change local preferences after the fix, and then see them with wrong value.

I get a dozen this week, still from that edit a year ago.

In T198370#4547738, @PhilipTerryGraham wrote:

@Gilles This works! Thanks for the tip; I'll go ahead and purge as many PNGs as I can!

5. Add an icon "diff" just after the regular message.

Thank you.

In T58845#4541161, @Nemo_bis wrote:

If you use a gadget to bring back the link, you can also get the gadget to hide any redundant indicator.

(Crying) It blinks.

In T166425#4539790, @Whatamidoing-WMF wrote:

I think they need to know how to make this happen ("steps to reproduce").

In T201340#4539376, @Mooeypoo wrote:

In T201340#4536678, @IKhitron wrote:

In T201340#4536659, @Niharika wrote:

@IKhitron Are you looking to stop using global preference for notifications? If you are using global preference, you should not be affected by this bug. Local exceptions should work as expected.

Day A: I opened Special:GlobalPrefs on my bot account. I changed one non-notification preference and saved. I opened Special:Preferences and saw it really works. I reopened Special:GlobalPrefs and removed the only change I did. I do not use the global preferences on that account any more.

That sounds like it works. Your local preferences are the ones that are active, global preferences are not affecting anything.

However, when you disabled GlobalPreferences, please check your local preferences and see what they are saved at. The bug potentially overrode those settings, so you might expect to have a certain checkbox on when it is actually off in local. Can you verify what local prefs you have for this bot?

Day C: I payed attention that one notification preference does not work. I opened Special:Preferences and saw that the checkbox is surprisingly not checked. I checked it and saved.

Day E: I payed attention that the same notification preference does not work. I opened Special:Preferences and saw that the checkbox is surprisingly not checked.

Which preference? The local? The global? If your global preferences are off, your local preferences are the ones that are working... is that what happened? It's a little confusing, I'm trying to make sense of what's wrong.

I'd like to see if I can understand what doesn't work, but I also don't want to destroy any of your preferences. Can you tell me wht is the bottom line of what you want to have, as preferences, at the end? Do you want to use the global preferences or the local ones?

It's not enough, needs also padding 0, and yes, I also did this.

Hi. Sorry to see it was removed. A little explanation: I used, and I believe many others, to use this feature not because of colour and not because of extra space. It was because clicking on this area calls "open user's talk page un read view" instead of "open user's talk page diff between last watched revision and the current one". It is just not helpful - you can't recognize all the changes.

In T202954#4536928, @Zoranzoki21 wrote:

Closing as invalid, because code related to this task is not edited.

It is, indeed.

Sorry, @JJMC89, but I can see an empty patch over there.

Are you talking to me? I am not a developer.

In T201340#4536659, @Niharika wrote:

@IKhitron Are you looking to stop using global preference for notifications? If you are using global preference, you should not be affected by this bug. Local exceptions should work as expected.

In T201340#4536626, @Niharika wrote:

Okay. Good news and bad news.

In T111663#4535163, @Framawiki wrote:

Given the  number of edits in the enwiki recent page, the change was published.
Thanks !
Can this task be closed ?

In T166425#4534518, @Deskana wrote:

This bug report is not actionable without more details.

But, an example

A named references defined in LTR direction<ref name=x dir=rtl>right-to-left.</ref> and reused in LTR direction<ref name=x dir=rtl />

should generate a warning too. I mean, it should not be checked what is the value of dir in the instance without text.

Great, thank you.

Hello, @Huji and @Arlolra. Thank you.
But I'm reading these two tasks, and I do not understand something important. Do you mean that from now on a named ref should have the same dir parameter on all instances? Why? Who needs the dir in all instances without text? It's redundunt information and it will disturb the user to write it over and over again, I believe it will be better if the instance with text will be used for direction, and the rest must be without dir parameter at all, throwing an error message if they are. What do you think?

Absolutely. But looks like it takes years, so I suggested something simple until then.

I did not work with this table a lot of time, so I run a simple query to remember:

select * from externallinks limit 10

to see the schema.
I saw that el_from_namespace was 0, seems like all 10 examples where articles. So I used this field in a new query, something like

#...
and el_from_namespace in (0, 6, 10, 14, 100, 118)
#...

Run the query, get the results. Everything looks ok. Exported to pagepile, started to work. And only then saw links to talk namespaces. If the value of this field was always -1, and not unfortunately fitting one of actually existing namespaces, I would (1) saw it in the first query and understood it's not working, and (2), the second query was empty in place of bringing wrong results.
Summary: for now, all entries marked as they were in articles namespace, and it's wrong.

I wasn't sure why query results looks weird, so I eventually found this. Maybe you should set this number to -1 or something in all wikis for now, I don't know.