Problem/Motivation
Language options "- Not specified - " and "- Not applicable -" appear to the user as being children to the previous language option within the language configuration form element, especially as more options follow after these two options.
Proposed resolution
Proposed solution is to move these two options to the end of the listing. Before/after:


It makes more sense to move up these options also because the *default* value of the select box is "Site default (XZY)", which this way is at the top instead of the middle of the list.
Remaining tasks
usability review done in #13 by @Bojhan
Commit. :)
User interface changes
See above.
API changes
None.
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | 2143013_language_options_order_after.png | 25.38 KB | ti2m |
| #9 | 2143013_language_options_order_before.png | 25.58 KB | ti2m |
| #1 | language_options_order-2143013-1.patch | 1.2 KB | ti2m |
Comments
Comment #1
ti2m commentedComment #4
ti2m commented1: language_options_order-2143013-1.patch queued for re-testing.
Comment #5
gábor hojtsyWould be good to have a screenshot of this change to see how it helps :D
Comment #7
gábor hojtsy1: language_options_order-2143013-1.patch queued for re-testing.
Comment #9
ti2m commentedComment #10
gábor hojtsy1: language_options_order-2143013-1.patch queued for re-testing.
Comment #11
ti2m commentedComment #13
Bojhan commentedThis looks better :)
Comment #14
gábor hojtsy1: language_options_order-2143013-1.patch queued for re-testing.
Comment #15
gábor hojtsyUpdated issue summary, moving to RTBC given the random fails are now gone and based on feedback from Bojhan.
Comment #16
gábor hojtsyFix tag name.
Comment #17
yesct commentedstill applies. tried it manually, works great. also read the patch and code changes look good too.
Comment #18
webchickHm. While I think this is certainly better than it was, there's still the chance for someone to think that these are sub-items of German because the " - " character is used.
If we used a different character set, such as "[Not applicable]" I think that confusion might go away. That could possibly introduce inconsistency with other places in core though; presumably that's why the " - " character was chosen.
I'm comfortable committing this since it definitely makes things better than they are, so...
Committed and pushed to 8.x. Thanks!
...but leaving at needs review for a little further discussion on the bug in the OP.
Comment #19
gábor hojtsyDoes not seem like a discussion about this continued in the past 4 days. The '-' signifier is used in concert with other '- None -' options in Drupal. This is Drupal's standard to signify "none" options, and these languages are such 'none' options.
Comment #20
Bojhan commentedGábor, can we just leave this open for a while? I like all the managing, but some things just need a bit of time. I agree with @Angie that this is OK, but not very ideal.
Comment #21
znerol commentedDiscussion did not take place in months, closing.