Two other possible ideas:
either a “has feature” or “doesn’t have feature” list ↩︎
The WebUI uses Patternfly, which doesn’t guarantee accessibility, but should make it relatively easy to do the right thing.
I’d say either way it’s important to make it clearer what these messages talk about: “this system” is not clear at all. You can only understand it together with the warning: “oh, you mean the (to be) installed system, not this system I’m using right now”.
And once it’s clear that these settings are about the installed system there should be no surprise that the currently running system remains unchanged.
… unlessed I’m confused, too 
Is the initial question “which … do you want to use for the installation process” gone?
- Reverse #2. That is, have a flag for spins which don’t implement systemd-localed functionality.
Looks to me fragile but I’m not opposed to this. I just wonder what would be the benefit.
- Maintain a list[1] of spins and enable or disable the warning based on that.
If possible, I would like to avoid having a hardcoded list in Anaconda. Most of the time that is something you don’t want to have because it’s harder to enable. Situations like my custom spin or I’m just playing around makes the situation worse.
No, that question should stay there. Only the highlighted parts are impacted.
Heh, that label is there for a quite long time, maybe it’s worth to think about the change. Anyway, it seems to me that this idea it is not correct. If we wrote there that these keyboard layouts are only for the installed system that is not correct neither because if systemd-localed is supported by the system it will be propagated.
Anyway, this points me to another option:
Change to message:
“Which keyboard layouts would you like to use on this system?”
To something like:
“Configure keyboard layouts for installed system. If Anaconda keyboard layout switching is supported by the system it will be set to the currently running system.”
However, it would be still confusing because you would see keyboard layout switch in the right corner (not visible on the picture because it’s disabled) I’ll add another picture next to it to show the difference.
I’ve changed the pictures above to make obvious what is changing. Also, I missed to highlight the button in the right corner at first.
In short without this feature, users would have visible current keyboard layout switching everywhere in Anaconda.
Hi, I’m thinking about starting a project to enable the new keyboard switching solution on X11 based systems. However, I wanted to be sure that no-one already done that or started the effort.
If someone knows about that please tell me.