Page MenuHomePhabricator

Cannot vote on mobile (using desktop view) in STV elections
Open, HighPublicBUG REPORT

Description

What is the problem?

I cannot vote on an STV election using a mobile, because I cannot use drag-and-drop. Therefore, I cannot use the new STV voting interface (T394536).

We could perhaps fallback to the non-JS interface on mobile.

Steps to reproduce problem
  1. On a mobile, login to https://vote.wikimedia.beta.wmcloud.org
  2. https://vote.wikimedia.beta.wmcloud.org/wiki/Special:SecurePoll/vote/2746
  3. Attempt to vote
Environment

Browser: iPhone 13 Safari. Samsung Galaxy S22 Chrome.
Wiki(s): https://vote.wikimedia.beta.wmflabs.org SecurePoll 3.0.0 (6b7e512) 07:27, 23 July 2025.

Event Timeline

Dreamy_Jazz subscribed.

Having tested the base OOUI demo it seems that this is an upstream bug with OOUI. I cannot move any of the items in the list when using a mobile device (using Chrome DevTools to simulate that).

It seems that mobile devices don't implement the HTML5 drag and drop events that OOUI uses for this.

Change #1174460 had a related patch set uploaded (by STran; author: STran):

[mediawiki/extensions/SecurePoll@master] Fall back to drop-down voting for STV when in mobile contexts

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

Change #1174460 merged by jenkins-bot:

[mediawiki/extensions/SecurePoll@master] Fall back to drop-down voting for STV when in mobile contexts

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

Has this been tested/confirmed as fixed? @HJ_Mitchell reported in a Telegram group

It took me a while to figure out that it was drop and drag but then I couldn't select the names and drag them across. Not sure if the problem was my end or the other but was much easier on a laptop.

Samsung S25 Ultra, Android 15, Chrome 141.0.7390.70.

On the desktop web on a mobile device...

Reporting that there is at least one report of voter experiencing this difficulty to the Elections Committee inbox.

Replicable on iOS too if you scroll down and click on Desktop. We know numerous users do tend to use the desktop web on mobile devices for various reasons.

jrbs raised the priority of this task from High to Unbreak Now!.Oct 10 2025, 4:46 PM
jrbs subscribed.

I guess the quickest solution might be to force noJS view on mobile (even on the desktop view) but I have no idea how easy that is.

Bumping to UBN since this impacts an active election

I guess the quickest solution might be to force noJS view on mobile (even on the desktop view) but I have no idea how easy that is.

Bumping to UBN since this impacts an active election

I don't think there will be a way to detect this, because mobile devices frequently fake they are a desktop to ensure that the desktop view is shown. Otherwise a site would have the ability to ignore the preference of the user to see a desktop view.

The simplest and only solution I can see is to force a noJS view for everyone, and given this is UBN I think we should do the simplest. Actually fixing this would require updating OOUI

The bare minimum is an always shown message/banner/notice on the JS version that says "if this doesn't work..."

But yeah, if we know it's broken/unuseable in numerous cases turning it off for everyone seems the most reasonable.

Is there a button / link to a noJS view? I'm really hesitant to just disable the drag-and-drop for everyone since it is much more intuitive as a voting solution and works for the majority of people.

I'm not sure if there is such functionality. I am stopping for the weekend. I'm not sure if another engineer from the Trust and Safety Product Team side of Product Safety and Integrity will be around to help with this until Monday.

Is there a sense of how urgent this is to fix?

jrbs lowered the priority of this task from Unbreak Now! to High.Oct 10 2025, 5:35 PM

Is there a sense of how urgent this is to fix?

It's preventing at least some people from voting it seems, but we do have almost 1,200 votes at this stage so clearly only a relatively low number of people.

To avoid giving the wrong idea I'll bump it back down to High until we figure out what we want to do about this. It certainly doesn't need weekend work IMO.

Is there a button / link to a noJS view?

This could probably be built into a url fairly easily. Then you can add a message with the link.

jrbs renamed this task from Cannot vote on mobile in STV elections to Cannot vote on mobile (using desktop view) in STV elections.Oct 10 2025, 9:09 PM

I added this to the voter info blurb:

'''If you are having trouble voting on mobile, [https://vote.wikimedia.org/w/index.php?title=Special:SecurePoll/vote/1864&mobileaction=toggle_view_mobile try our alternate interface].'''

That does seem to work in terms of switching to the dropdown view.

I don't think this is resolved? The issue wasn't actually fixed during the election

I don't think this is resolved? The issue wasn't actually fixed during the election

In that case, I will move this to Ready.

I don't think this is resolved? The issue wasn't actually fixed during the election

Wasn't it hotfixed with the voter blurb?

I added this to the voter info blurb:

'''If you are having trouble voting on mobile, [https://vote.wikimedia.org/w/index.php?title=Special:SecurePoll/vote/1864&mobileaction=toggle_view_mobile try our alternate interface].'''

That does seem to work in terms of switching to the dropdown view.


If it was resolved reasonably well for the election, do we know what we want to do as a follow-up, if anything? The OOUI fix is the most robust but if we can get away with some text and a manual toggle to mobile that would obviously be faster.

I don't think this is resolved? The issue wasn't actually fixed during the election

Wasn't it hotfixed with the voter blurb?

Sure, but it didnt actually fix the OOUI issue.

I added this to the voter info blurb:

'''If you are having trouble voting on mobile, [https://vote.wikimedia.org/w/index.php?title=Special:SecurePoll/vote/1864&mobileaction=toggle_view_mobile try our alternate interface].'''

That does seem to work in terms of switching to the dropdown view.


If it was resolved reasonably well for the election, do we know what we want to do as a follow-up, if anything? The OOUI fix is the most robust but if we can get away with some text and a manual toggle to mobile that would obviously be faster.

IMO we should either file a new task focusing on fixing this long term (and then close this out), or we should keep this open.

Otherwise I think this issue will be forgotten about for a next election and/or not known about by third party wikis.

If a follow-up up task already exists to fix this in OOUI to solve the securepoll issue, then apologies as I didn't see it.