User:Enterprisey/signature rfc drafting: Difference between revisions

Disclaimer: zero deep thought was put into this, it just popped into my head

Goals:

• No change in appearance for existing accounts.
• No custom signatures by default for new accounts or logged-out readers.

Plan:

1. Build database of current custom signatures.
2. Develop gadget to render <span class="signature">Example</span> (actual syntax may differ) as the appropriate custom signature. Gadget should be as fast and efficient as possible.
3. Turn gadget on for everyone. (But don't automatically turn it on for new accounts.)
4. Change ~~~~ to insert <span class="signature">Example</span> (or whatever we decide on).

Details:

• Don't edit archives. Too much work.
• Non-Latin usernames specify a romanization in preferences, or have one auto-generated. New default sig will display it in parentheses (or whatever we decide on).

Alternative plan, from Elli:
~~~~ now inserts <span class="custom-signature">...</span><span class="standard-signature">...</span>, and the preference just toggles display:none for those two CSS classes.

Thoughts welcome. Enterprisey (talk!) 22:10, 3 June 2021 (UTC)

Thoughts

• Should probably use a data-attribute instead of a class, thus: <span aria-hidden="true" data-customsig="true">[[User:Jorm|I don't care about our users in any way]]</span><span data-signature="true">[[User:Jorm|Jorm]]...</span> and use aria-hidden = true/false to switch between them.--Jorm (talk) 22:49, 3 June 2021 (UTC)

See also

• the current (as of June 2021) sprawling discussions at WT:SIG, for context
• User:Rhododendrites/signature rfc drafting, from which I stole the name