• Bug 46855 has been marked as a duplicate of this bug. ***

(In reply to comment #1)

• Bug 46855 has been marked as a duplicate of this bug. ***

This bug did not come up in my search, but it is extremely similar.
I'm requesting that all signatures be wrapped in a set of classed tags so that
those editors with vision problems (like myself) can add a little css or
javascript (or have a checkbox that lets it be done server side on their
preferences page) to remove custom signatures from everyone. I've seen on WP
talk:signatures there was a request to have all custom signatures removed from
this site, and my suggestion here would allow those people that think they
shouldn't be allowed for anyone if they are not fully customizable and allowed
for everyone to disable all signature customizations. To summarize, I am
requesting signatures be wrapped in an element to allow users to add something
like:
span.signature {background-color: #FFF; color: #000; text-decoration: none;
font-family: "Times New Roman", monospace;}

Allowing them to remove blinking, scrolling, and colors that are too bright and
fail to meet standards of contrast ratios without having to request every user
that has an obnoxious signature to fix it wasting time and causing conflicts
and edit wars.

I don't care what the element tag is and I don't care much what the class is. An expansion of <span class="before-localcomments"> to include the whole signature and not just the ) and times stamp would work fine for me.

Change 130094 had a related patch set uploaded by Gerrit Patch Uploader:
Wrap user signatures in a span

https://gerrit.wikimedia.org/r/130094

This could add a lot of extra text to pages for ~~~ and ~~~~. Thoughts?

My thought is: No, thanks.

I recommend WONTFIX per Brion https://lists.wikimedia.org/pipermail/wikitech-l/2014-September/078855.html

+1 for this enhancement.

I'd suggest to add two classes: a specific class based on username or user ID (e.g. "user_john" or user_28746) and a general class (e.g. "user_signature") if <sig> or <author> can't be in use. Also, different user levels can have classes such "user_admin", "user_bureaucrat" etc.

This fix will add the extra text to pages but as far as I know text amount is not a concern, the issue here is to allow user do mute others signature styles while allowing everybody to custom them freely.

(In reply to Diana from comment #7)

+1 for this enhancement.

I'd suggest to add two classes: a specific class based on username or user
ID (e.g. "user_john" or user_28746) and a general class (e.g.
"user_signature") if <sig> or <author> can't be in use.

Why based on username? I think that would be too specific.

Also, different user
levels can have classes such "user_admin", "user_bureaucrat" etc.

Interesting idea, that I support.

This fix will add the extra text to pages but as far as I know text amount
is not a concern,

I don't see any reason this should add extra text to what readers or editors see, as these classes and whatnot can be added by the parser upon rendering.

the issue here is to allow user do mute others signature
styles while allowing everybody to custom them freely.

That is indeed the issue this ticket aims to offer a fix for.

(In reply to Technical 13 from comment #8)

(In reply to Diana from comment #7)

+1 for this enhancement.

I'd suggest to add two classes: a specific class based on username or user
ID (e.g. "user_john" or user_28746) and a general class (e.g.
"user_signature") if <sig> or <author> can't be in use.

Why based on username? I think that would be too specific.

Yes, as specific as signatures are. An username/ID-based class will allow users to style their signatures (and the others) through their user stylesheet. Also users can create scripts (through the user js) that can rely on classes more easily, e.g. a toc for comments in discussions.

Also, different user
levels can have classes such "user_admin", "user_bureaucrat" etc.

Interesting idea, that I support.

This fix will add the extra text to pages but as far as I know text amount
is not a concern,

I don't see any reason this should add extra text to what readers or editors
see, as these classes and whatnot can be added by the parser upon rendering.

If so, that's great!

the issue here is to allow user do mute others signature
styles while allowing everybody to custom them freely.

That is indeed the issue this ticket aims to offer a fix for.

I've been working on some user scripts that deal with custom signatures and it is a serious design flaw that there is nothing wrapping custom signatures and, more broadly, it's an issue that nothing indicates where a comment ends and the signature starts. This is especially the case given how many signatures are:

1. unreadable — A huge number of signatures are completely unreadable in dark mode, use insanely tiny fonts, have low contrast between text and background, etc.
2. difficult to interact with — Many signatures have links that are literally a single character wide, have a clickable region as small as 4px in height, redirects rather than direct links to talk pages, and more.

I can't even imagine how bad it is for people with color blindness and other vision issues.

Beyond using a span, I'd like to specifically request:

1. Adding the author name and a timestamp in a way that is easy to access and parse in user scripts and gadgets.

2. And it would be even better if CSS could be used to toggle between custom signatures and a default signature, but this would require two spans, one for the custom signature and one for a vanilla signature.

Addressing this is long overdue.

Thanks.