this behavior is intended - keyboard settings persist per user - that's why your setting did not apply to guest mode. marking this as Wont Fix. 

Hi, thanks for your answer. I'm not sure you understood the problem.

This is a Chromebox bought in France.
I'm plugging a French keyboard into it.
The system language is French.
The keyboard layout, both for login and for the main user, are in French.

… How is "guest mode uses US keyboard" a reasonable behavior?!
Having keyboard settings persist per user is fine, but the default is *not reasonable* here. You're blocking non-tech-savvy users outside the US from using guest mode.

According to  https://crbug.com/329018#c43  the default behavior should be the underlying latin keyboard layout, which is *not the case* here.

Basing on  https://crbug.com/329018#c43  looks like a regression?

We should revisit this. If we're serious about Chrome OS being usable by everyone everywhere there needs to be a way to set the keyboard in guest mode.

As olka@ points out, the decision in  bug 329018  was to have guest mode follow the owner account.

alemate@ shouldn't we use the same keyboard layout selected in OOBE in guest mode as well?

I agree to comment 16. 

I remember that Guest mode keyboard was fixed deliberately as Guest mode is intentionally unconfigurable.

Guest mode keyboard depends on device regional configuration. If device was produced to be French, it will have French keyboard in Guest mode. You can check device region on the chrome://system page in "VPD_2.0" entry.

What are the values there?

+ Bartosz

Re #6> As olka@ points out, the decision in   bug 329018   was to have guest mode follow the owner account.

Bartosz definitely did not support this.

Bartosz: WDYT?

VPD_2.0:

"customization_id"="AOPEN-FIEVEL"
"region"="nl"
"rlz_brand_code"="AOPC"
"ActivateDate"="2017-38"
"block_devmode"="0"
"check_enrollment"="0"

… So even though it was sold in France, maybe the device region wasn't France? And there's no hope of getting it to a French keyboard by default?

Yes, your VPD says it's from Netherlands. And your guest keyboard must match your physical keyboard layout (for obvious reasons). I don't know whether French keyboard is physically different from Netherlands , but I think we should not surprise our Guest users.

+alexpau +hungte

Since this is a Chromebox (sold without a keyboard), I wouldn't necessarily expect VPD region to match precisely where the device was sold (Alex/Hung-Te can correct me).

In this case, a "nl" keyboard is far more surprising to the user than reusing the layout at login screen. And yes, the layouts are _very_ different (AZERTY vs QWERTY).

We still want the 'region' because some Chromeboxes were sold with a keyboard. Also the region will be used by WiFi regulatory. But it's really a decision by OEM and ODM for how they want to set the region values.

Meanwhile, I think this has been brought several times for how to deal with keyboards in Guest mode. And I'd say 'setting right region' won't be the ultimate receipt because it is still possible that people may want to use different USB keyboards for a device purchased in different countries. Maybe OOBE team should consider if they want to allow access to *all keyboard layouts* in Guest mode?

In general, "guest mode is intentionally not configurable" still stands as a design goal. However, we already deviate from this in some aspects. IIUC, the locale choice persists from OOBE / login screen into guest mode. It would seem reasonable to have the keyboard follow suit. We should probably not allow the admin to configure the layout freely (e.g. Dvorak layouts), but we could automatically pick the Latin layout matching the UI locale.