User talk:PPelberg (WMF)/sandbox

I tried commenting on your talkpage, but the abuse filter spamlink blocked it, so I am commenting here:

There's a discussion going on Village pump (technical) about custom signatures aka sigs. One user went above and beyond with their customized signature inquiring the community for input, two of which pointed out the reply button not displaying. I do not have the know-how to advise the aforementioned user to get the reply to work as intended, so I turned to you. The below signature is the sig in question: https://prnt.sc/O9RLhHZw4-hN

Your input would be much appreciated since you are the creator of the gadget.

Yours faithfully,

~~~~

They were joking.

I think it’s a bug though if the user could save that signature in the first place… I’ve asked him if he actually saved the preference, or just worked around the (existing) limitation.

Although he said it wasn’t saved, I tested it (in my local wiki), and I could save a signature with the content {{subst:User:Tacsipacsi/signature}}, where User:Tacsipacsi/signature contained that code – the only warning was that multi-line wikitext may break some tools. So I removed the line breaks from the wikitext – and violà, I could save the signature breaking the reply tool without any warnings. I think there should be at least a warning if the resulting HTML isn’t recognized by DiscussionTools, even if the wikitext looks innocuous. Should I create a Phabricator task for that?

Hi, Peter, hope you don't mind me posting here. Something that jumped out at me on first glance was that the phrase “multi-line comments” could be taken to mean source-code comments rather than talk posts/replies. “Talk page comments” is unambiguous. Perhaps prefer “multi-line list items”, since the new markup would apply to all lists, not just talk pages?

I agree that this could be confusing. OTOH, most editors don't think that they're making a list when they type : to "indent" a comment.