Change 669715 had a related patch set uploaded (by DLynch; owner: DLynch):
[mediawiki/extensions/SecurePoll@master] Convert range voting custom column labels to OOUI

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

Change 669715 merged by jenkins-bot:
[mediawiki/extensions/SecurePoll@master] Convert range voting custom column labels to OOUI

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

UI-wise, very little appears to have changed in terms of behaviour and appearance.

• The labels corresponding to the inputs are no longer bold. But, this is now consistent with the rest of the form.
• It wraps around when there are lots of columns. Previously, it just kept expanding to the right.
  
• The labels for the inputs don't automatically get changed from "n" to "+n" when you add a negative column value (bit confusing, see screenshots below). However, this difference is purely aesthetic.
  • Before:
    
  • After:
    
• It does not work without JS. This was also the case before. If editing an existing election which already uses custom column labels, you can update the custom label values and remove columns. But you cannot add columns. There does not appear to be a way to add custom labels when you are creating an election without JS.

Otherwise, I tested creating and editing an election to make sure that the correct custom labels are saved to the database.

Test Environment: https://vote.wikimedia.beta.wmflabs.org SecurePoll 2.0.0 (1276a79) 22:33, 8 March 2021.
Test Browser: Firefox 78

• The labels for the inputs don't automatically get changed from "n" to "+n" when you add a negative column value (bit confusing, see screenshots below). However, this difference is purely aesthetic.

@Prtksxna Should we raise a ticket about this? I think it looks a bit odd to see -1, 0, 1, 2, +3:

Might it be better either always to have the + or never to have it?

It'll be a 5 minute patch to fix that, so up to you if you'd like the administrative overhead of a new ticket.

In T273043#6897866, @DLynch wrote:

It'll be a 5 minute patch to fix that, so up to you if you'd like the administrative overhead of a new ticket.

Sounds good to me. Personally I'd ditch the +, but happy either way

Change 670272 had a related patch set uploaded (by DLynch; owner: DLynch):
[mediawiki/extensions/SecurePoll@master] Toggle signs on column labels after creation

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

I went with leaving the + sign, mostly because I think it leads to more clarity now that the inputs can wrap lines.

Change 670272 merged by jenkins-bot:
[mediawiki/extensions/SecurePoll@master] Toggle signs on column labels after creation

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

In T273043#6897569, @Tchanders wrote:

• The labels for the inputs don't automatically get changed from "n" to "+n" when you add a negative column value (bit confusing, see screenshots below). However, this difference is purely aesthetic.

@Prtksxna Should we raise a ticket about this? I think it looks a bit odd to see -1, 0, 1, 2, +3:

Might it be better either always to have the + or never to have it?

Sorry, even with the screenshots I'm having a hard time following what is going on here. We're talking about the numbers at the bottom, correct?

In T273043#6898091, @DLynch wrote:

I went with leaving the + sign, mostly because I think it leads to more clarity now that the inputs can wrap lines.

The inputs under the numbers can have wrapped lines? Sorry, could you please explain what you mean here.

Sorry, even with the screenshots I'm having a hard time following what is going on here. We're talking about the numbers at the bottom, correct?

In the screenshot on the right, some of the positive numbers have a + and some don't; that's the bug we're fixing.

@DLynch's patch has fixed this so that all of the positive numbers have a + now:

Moving to Done since the patch has been merged; @Prtksxna feel free to file a follow-up if you want to change anything.

In T273043#6900140, @Tchanders wrote:

Thanks @Tchanders, I get it now. This screenshot explained what wrapping inputs meant.

Moving to Done since the patch has been merged; @Prtksxna feel free to file a follow-up if you want to change anything.

Sounds good, no follow-up needed.