[Unicode]   Common Locale Data Repository : Bug Tracking Home | Site Map | Search

CLDR Ticket #11250(closed: needs-more-info)

Opened 10 months ago

Last modified 4 months ago

Resource-wasting bugs in the Survey Tool

Reported by: Marcel Schneider <charupdate@…> Owned by: anybody
Component: surveytool-other Data Locale: ALL
Phase: dsub Review:
Weeks: Data Xpath:



SURVEY TOOL has a number of bugs that make using it wearisome and tiresome.

The input window often closes by itself while the submitter is typing in.

The input window is too small, making edits uselessly complicated.

Sometimes ST switches to another page, seemingly due to uncontrolled keyboard shortcuts, that should be disabled, at least optionally.

The forum reloads automatically even while the submitter is writing up a post, so that the whole post is lost through not being able to copy it while ST has disconnected the session. That bug is even contrary to the own spec according to which the forum does not reload automatically, and the submitter should refresh the page to get new posts.

All that adds to the display issues filed in ticket Various whitespaces not marked up while bidi controls are

These poor ergonomics might be part of an explanation why some people do very little through nothing during the survey, while there are plenty of new guidelines to apply.


Change History

comment:1 Changed 10 months ago by Marcel Schneider <charupdate@…>

We need a "vote for all winning values" in a section feature.

In http://st.unicode.org/cldr-apps/v#/fr/Displaying_Lists/4480e9e541ba33de all winning values are correct, and I should click 24 times to vote them all, often twice because ST did not save a click (being too busy with background tasks).

The actual ST is not efficient enough and not respectful towards submitters having limited time.

If you want to get people do the job, you need to add a download facility to download the submitter data for one section or for all sections, so that busy people can quickly edit the worst in a text editor, efficiently make bulk changes using regexes, and finally upload the file for ST to parse (as it does anyway each time it’s loading the page).

comment:2 Changed 10 months ago by Marcel Schneider <charupdate@…>

The bugs consisting in votes not being saved, and input fields being closed before submitter hits Enter, are due to the ST running a sort of Bailey tests over the whole page a few seconds after some process is completed. Hundreds of instances like this one are reported in a fraction of a second:

Object {isBailey: true, tests: Array[0], rawValue: "m:ss", valueHash: "bTpzcw", pClass: "winner"…}

In the wake of this process garbage, the input window disappears, and votes remain unnoticed, forcing the submitter to resume and repeat actions, such as clicking to vote or typing the value again.

This respectless malfunctioning is inacceptable.

That is even unlikely to be fixed, given ST doesn’t appear to be actively maintained (all files and folders are several years old).

Therefore Unicode should allow submitters to work outside ST by editing XML files b
y hand in a text editor. Actually that process is only available for new locales.

It is unclear to me what policies all that is based upon, and why working in a slow and process-wasting ST is accepted by other submitters.

Having said that, ST has a nice UI and provides a lot of information. It is the more astonishing that no action is taken to correct the remaining bugs as reported above and in the linked ticket about whitespace disambiguation.

comment:3 follow-up: ↓ 5 Changed 10 months ago by srl

Please give the OS, browser version, etc.

comment:4 Changed 9 months ago by srl

  • Xref set to 11218

comment:5 in reply to: ↑ 3 Changed 9 months ago by Marcel Schneider <charupdate@…>

Replying to srl:

Please give the OS, browser version, etc.

I’ve tried two and it’s the same. Lastly in this survey: in Chrome 49.0.2623.112 (64-bit) on Snow Leopard 10.6.8.
Also tried on Windows 10/Dell Optiplex with last version of Chrome. Also tried Firefox on the latter, same issue.

We can do things such as vote, submit data value, but once ST decides to refresh, nothing works: votes are not registered, input window vanishes and data is lost. That occurs a few seconds after an action (vote, submission). If we’re quick enough (e.g. copy English value and readily press Enter because it happens to be convenient for French too (as for narrow display), we may input two items, but if there is an edit, time-out makes window disappear and key actions (backspace, arrow keys) are handled as ST shortcuts so the page disappears altogether (ST “believes” we want to go go previous or next page).

So we have to wait, and are likely to switch to another task, which will take some time to let us return to ST. I’ve tried with several tabs, but it’s no use, ST may refresh a tab at any time, given it’s become outdated (due to my using ST in another tab). I’ve not pushed the idea until switching between two browsers. One would need to use two computers at once, but I’ve got one single (17″) screen for the two.

But now I’m done (left many emoji unvoted, though). After all I can’t figure out how it really works for other people. It’s annoying with bunches of tiny items such as measurement units, as opposed to script and language names.

comment:6 Changed 5 months ago by mark

  • Milestone changed from UNSCH to to-assess

comment:7 Changed 4 months ago by mark

  • Status changed from new to closed
  • Resolution set to needs-more-info

There were some improvements in the ST. Please see if those address these concerns.


Add a comment

Modify Ticket

as closed
Next status will be 'new'
Next status will be 'closed'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.